Database Users

[Q] Slight(Large) Issue with my Nook

My Nook Color is rooted. It has CM7 on it. Recently, by that I mean 5 minutes ago, I was trying to download a theme and it told me that I was required to have a Micro SD Card inserted. So I went and found my the card I used to root my Nook and inserted it into my Nook. It no longer clicks in, justs shoots back out. One time it didnt even pop back out, I had to fish it out. It almost as if the spring mechanism is broken. I have read that others are having similar issues. So, I called Barnes & Noble's Tech Support. They told me that I need to take my Nook to the nearest Barnes & Noble and see if they can get it out and B&N will deal with it from there. Heres where my issue comes in. I have tried numerous times doing the 8 failed boots thing. None of them worked. Everything else I have seen about "Unrooting" say that I have to use CWR. I CANT! I have no SD Card slot. I need a way of restoring my NC back to the stock firmware before I take it to Barnes & Noble and they tell me "You've Rooted It. You Voided Your Warrenty" Thanks for taking the time to read this long post and I look forward to someone being able to answer me.

Well, you generally want to have a blank card in it when you run CM7. I am assuming that you reformatted this card so that it is now blank & not bootable?
In any event, I would very carefully keep trying to pop out the card. The spring is not usually the issue, it is the catch that fails.
As to CWR, you should be able to choose to boot into recovery when you go to power down. CWR is already on there (or likely is).

Are you sure you insert the uSD card properly?
It seems to be a hardware, like you mentioned, spring mechanism, issue.

[Q] NC Screen Problems (Intermittently Won't Turn On)

I've got a NC rooted using a 16GB SanDisk mSD card with CM7 on it (not sure precisely the version but don't think it matters). I set this up with help from the xda-developers site in December 2011 and have only used the NC in this mode ever since. I bought the NC as a refurb from the B&N eBay sale in late November 2011 and the unit has a one-year warranty.
Two days ago I was using the NC looking at photos and I let the screen time out and turn off. After this the NC wouldn't turn on; didn't matter what I did. I tried holding the power button down for 10-seconds, I pulled the mSD card and tried a hard reset (power, n, vol- for 5-seconds), tried charging the battery until the stock charging cable light went from orange to green. Did everything I could think of without any signs of life in the NC.
So I brought the NC to a B&N store (without the mSD card or mentioning that I'd been running it rooted) and the moment the guy in the store hit the power button the damned thing booted to the stock OS. The guy told me that this type of thing happens frequently and he thinks there's something about the WiFi in the store "waking up" the NC's (seemed like bull-bleep to me, but the NC was running). The guy told me he'd update the OS from the 1.2v it was at to the current 1.4v and this too could help. I let him do it figuring it probably didn't matter because I should be able to reset it to the factory config if there was something about the 1.4v that screwed up the root.
The guy gave me my NC back after updating it, told me if the problem persisted he'd do an exchange, and I went into my car in the parking lot. There I put in my mSD card into the NC after doing a full shutdown and it booted into CM7 with no problems. Today, however, same problem occurred, couldn't get the screen to turn on. So I pulled the mSD card, tried all the buttons, hard reset, etc. Then I shook the unit and was then able to get it to boot to the stock OS. Did a power down, installed the mSD card, and it booted to CM7 again no problem. That was ten-minutes ago, now the screen is again dead.
Even though the NC has lived a pretty easy life inside an Otterbox case, never been dropped or exposed to water or high humidity, I'm thinking this is a hardware problem and that I should just do an exchange. I've not found any similar posts or information about this type of thing, so I'd appreciate anybody's thoughts about the matter. Specifically:
1 - If I get an exchanged unit, should I be able to boot from my mSD card or will I have to format it and re-install CM7 like I did initially?
2 - If I'm offered a Nook Tablet in place of a NC, should I take the Tablet? I know it's got more power but I understand that rooting it even via mSD card is a PIA and not as straight forward as doing so on the NC.
3 - Is there anything obvious that I'm missing here?
Thanks for the help and apologies if I missed that this is a common problem the fix for which is commonly known.

Turgidson said:
I've got a NC rooted using a 16GB SanDisk mSD card with CM7 on it (not sure precisely the version but don't think it matters). I set this up with help from the xda-developers site in December 2011 and have only used the NC in this mode ever since. I bought the NC as a refurb from the B&N eBay sale in late November 2011 and the unit has a one-year warranty.
Two days ago I was using the NC looking at photos and I let the screen time out and turn off. After this the NC wouldn't turn on; didn't matter what I did. I tried holding the power button down for 10-seconds, I pulled the mSD card and tried a hard reset (power, n, vol- for 5-seconds), tried charging the battery until the stock charging cable light went from orange to green. Did everything I could think of without any signs of life in the NC.
So I brought the NC to a B&N store (without the mSD card or mentioning that I'd been running it rooted) and the moment the guy in the store hit the power button the damned thing booted to the stock OS. The guy told me that this type of thing happens frequently and he thinks there's something about the WiFi in the store "waking up" the NC's (seemed like bull-bleep to me, but the NC was running). The guy told me he'd update the OS from the 1.2v it was at to the current 1.4v and this too could help. I let him do it figuring it probably didn't matter because I should be able to reset it to the factory config if there was something about the 1.4v that screwed up the root.
The guy gave me my NC back after updating it, told me if the problem persisted he'd do an exchange, and I went into my car in the parking lot. There I put in my mSD card into the NC after doing a full shutdown and it booted into CM7 with no problems. Today, however, same problem occurred, couldn't get the screen to turn on. So I pulled the mSD card, tried all the buttons, hard reset, etc. Then I shook the unit and was then able to get it to boot to the stock OS. Did a power down, installed the mSD card, and it booted to CM7 again no problem. That was ten-minutes ago, now the screen is again dead.
Even though the NC has lived a pretty easy life inside an Otterbox case, never been dropped or exposed to water or high humidity, I'm thinking this is a hardware problem and that I should just do an exchange. I've not found any similar posts or information about this type of thing, so I'd appreciate anybody's thoughts about the matter. Specifically:
1 - If I get an exchanged unit, should I be able to boot from my mSD card or will I have to format it and re-install CM7 like I did initially?
2 - If I'm offered a Nook Tablet in place of a NC, should I take the Tablet? I know it's got more power but I understand that rooting it even via mSD card is a PIA and not as straight forward as doing so on the NC.
3 - Is there anything obvious that I'm missing here?
Thanks for the help and apologies if I missed that this is a common problem the fix for which is commonly known.
Click to expand...
Click to collapse
Could be you are experiencing the Sleep of Death (SOD) problem. The unit is still on but can't wake up. The only thing you can do to get out of it is to hard power it off and back on. Hold the power button for a long time. Release and push again until it turns back on.
SOD happens when you leave wifi on all the time and the unit goes into deep sleep. Sometimes you can't wake it back up.
If you have this happening a lot, there is a modded wifi kernel module that helps. If you need it, PM me and I will send you a link.
If you get an exchange it should work just like yours with the SD install. Just put the same card in and should run OK.
You won't get a nook tablet without paying more. If you are happy with the color, I would stay with it. The tablet is still iffy about running other ROMs yet.

Thanks for the info. Does the SOD affect the unrooted NC? If it doesn't then I should be able to trouble shoot the problem by running the NC with the stock OS for several days and see if the problem continues. Does this sound reasonable?
Sent from my SCH-I510 using XDA

Turgidson said:
Thanks for the info. Does the SOD affect the unrooted NC? If it doesn't then I should be able to trouble shoot the problem by running the NC with the stock OS for several days and see if the problem continues. Does this sound reasonable?
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
It does not affect the stock. That should be a good test.

No recovery BSOD

(BLACK SCREEN OF DEATH)
OK, I have a dead Nook on my hands - non-responsive completely. A coworker of mine bought one of those CM7 cards off of Ebay and it worked fine, but had some connection issues, so I suggested he make a move to PA. Of course, I was the one that was going to do this, so I installed CWR to the EMMC, rebooted, hit N, and booted to EMMC recovery no problem.
Here's where things got stupid:
In recovery, I attempted to install PA without removing the sd card and used the internal SD Card to grab the image. Yeah, I know... Browbeating not necessary... It was taking too long and appeared stuck, and then suddenly the unit just appeared to power down. That was it. No more recovery, the card no longer worked, NOTHING!
Hooked it up to my PC and for a second or two when you hook it up, you can see in the device manager, the Motorola device pops up (I own a Motorola phone, so I assume the drivers are kicking in), and then it goes away. Long press power, do it again, same results. Still no screen, no nothing.
So I figure the 16GB CM7 card (Sandisk SDHC) still has to be useful for creating a recovery card, right? After all, whoever created it originally was able to stuff a bootloader on there, right?
So here's what I tried in terms of tools:
win32diskimager .1 r15
win32diskimager .7
WinImage 8.5
with these, I have tried the following images:
16gb_clockwork-3.0.2.8.img
generic-sdcard-v1.3.img
TWRP-2.1.8-bootable-SD.img
And I used MiniTool Partition Wizard to remove the partitions after each attempt and reformat back to its full 16GB.
The only time a burn was unsuccessful was on the 16GB clockwork with Win32DiskImager - it gave an error stating it couldn't find sectors at 99%. I tried an 8GB image too, but while it burned successfully, no dice.
Alright, so here we are, me at the end of my wits, you reading this tale of woe, and a coworker without a functioning device. The device has charged all night. I owned an NC for years and was mod-happy during that time, and although I had BSOD, I was able to fix it easily. This is a 1 year old BNRV200 (pretty sure they didn't switch up the models).
Help? Advice? WT%#$%^?
EDIT: ADB does not recognize the device when connected.

Go to my NC partition repair thread linked in my signature and follow the procedures there.
Use SDFormatter free on the web for formatting your card before burning one of my bootable CWM images. Don't use partitioning software. The NC is real finicky about how cards are burned. Look at my NC Tips thread and read item A9.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Go to my NC partition repair thread linked in my signature and follow the procedures there.
Use SDFormatter free on the web for formatting your card before burning one of my bootable CWM images. Don't use partitioning software. The NC is real finicky about how cards are burned. Look at my NC Tips thread and read item A9.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
OK, so I used SD Formatter v3.1, size adjustment ON, Full Format (Erase)
Then I used win32diskimager v.7 with CWM-6.0.1.2-bootable_SD - still no boot.
Went back to SD Formatter, rinse, repeat.
Then I used win32diskimager v.1 r15 with same image - still DOA.
Anything I'm missing? I'm going to try 5.5.0.4 in the meantime, but I have my doubts that it will make a difference.

majorpay said:
OK, so I used SD Formatter v3.1, size adjustment ON, Full Format (Erase)
Then I used win32diskimager v.7 with CWM-6.0.1.2-bootable_SD - still no boot.
Went back to SD Formatter, rinse, repeat.
Then I used win32diskimager v.1 r15 with same image - still DOA.
Anything I'm missing? I'm going to try 5.5.0.4 in the meantime, but I have my doubts that it will make a difference.
Click to expand...
Click to collapse
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?

reply
majorpay said:
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
Click to expand...
Click to collapse
brother what to tell you my nook color is also dead similarly since last 3 weeks.i also tried everything under the roof like bootable sd card.i also opened a topic in help section but did not get a single reply.i wrote to lepinllair also but even he does not know what to do . i miss my nook everyday. i appeal to nook community to please help us get out of this mess. i also get similar trying to search divers issue when attached to a laptop.also mine is getting charged fully .so i guess both of us have a similar issue. brother please let me know if you find solution .thankyou

majorpay said:
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
Click to expand...
Click to collapse
dajmaa said:
brother what to tell you my nook color is also dead similarly since last 3 weeks.i also tried everything under the roof like bootable sd card.i also opened a topic in help section but did not get a single reply.i wrote to lepinllair also but even he does not know what to do . i miss my nook everyday. i appeal to nook community to please help us get out of this mess. i also get similar trying to search divers issue when attached to a laptop.also mine is getting charged fully .so i guess both of us have a similar issue. brother please let me know if you find solution .thankyou
Click to expand...
Click to collapse
Well looks like their is Three of Us. I have been trying to fix my daughters Nook Color for about 2 weeks now. I have tried 6 different sd cards, my internal card reader and 2 external ones. I have used every version of cw recovery and twrp i can find. I have tried alot of guides. At least the ones that the downloads are still there for.
Heres to pulling your hair out.

SHOOTEMUP2.0 said:
Well looks like their is Three of Us. I have been trying to fix my daughters Nook Color for about 2 weeks now. I have tried 6 different sd cards, my internal card reader and 2 external ones. I have used every version of cw recovery and twrp i can find. I have tried alot of guides. At least the ones that the downloads are still there for.
Heres to pulling your hair out.
Click to expand...
Click to collapse
Well, here's what I can say (which may be saying nothing):
Back in the day when I had a BSOD on my old device, I was able to fix it by using TheCube's methods. I don't think he hangs around these parts anymore, but I know it was a specific sized SD card you had to have, and a pretty old version of CWR you were flashing onto the card. I remember there was only ONE version of win32diskimager that would work and it was one of the V 0.1 variants (r?). Technology has changed, people have come and gone, and this may mean absolutely squat now. I just know I had this problem on my old one and I was able to fix it that way.
All the links to those items are gone, all the files have been long since lost, and the server I used to use to house those files has long since become a thing of the past.
Maybe B&N has set trip-wires for the modding community in their "newer" revisions? I cut the red wire, and the whole thing blew up.

majorpay said:
Well, here's what I can say (which may be saying nothing):
Back in the day when I had a BSOD on my old device, I was able to fix it by using TheCube's methods. I don't think he hangs around these parts anymore, but I know it was a specific sized SD card you had to have, and a pretty old version of CWR you were flashing onto the card. I remember there was only ONE version of win32diskimager that would work and it was one of the V 0.1 variants (r?). Technology has changed, people have come and gone, and this may mean absolutely squat now. I just know I had this problem on my old one and I was able to fix it that way.
All the links to those items are gone, all the files have been long since lost, and the server I used to use to house those files has long since become a thing of the past.
Maybe B&N has set trip-wires for the modding community in their "newer" revisions? I cut the red wire, and the whole thing blew up.
Click to expand...
Click to collapse
Story of my life. always a Dollar Short and a Day Late. Well in this case a couple years late.

leapinlar said:
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Leap... Have you tested these methods? If so, can you give me a lead as to which SD reader you used? I'm not above believing that the problem is the multiple readers I have (one is internal, the other is a Chinese plastic knock-off).
I was not able to get over to my parents house to test on their Nook yet.

majorpay said:
Leap... Have you tested these methods? If so, can you give me a lead as to which SD reader you used? I'm not above believing that the problem is the multiple readers I have (one is internal, the other is a Chinese plastic knock-off).
I was not able to get over to my parents house to test on their Nook yet.
Click to expand...
Click to collapse
I use an external USB card reader made for micro SDs so I need no micro to SD adapter. A little red or grey one. I got it on eBay for $2. In fact, I bought several since they sometimes quit working. Then I use win32diskimager with no other windows open. Someone said they even had to update to the latest version (0.7, I think) from sourceforge. Any number of things could make it not boot. NCs can sometimes be very temperamental. But I have never had one I could not eventually get to boot to SD.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
I use an external USB card reader made for micro SDs so I need no micro to SD adapter. A little red or grey one. I got it on eBay for $2. In fact, I bought several since they sometimes quit working. Then I use win32diskimager with no other windows open. Someone said they even had to update to the latest version (0.7, I think) from sourceforge. Any number of things could make it not boot. NCs can sometimes be very temperamental. But I have never had one I could not eventually get to boot to SD.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Alright... Well here's where we are at this point:
Bought a Dynex 7 in 1 with specific port for MicroSD - burned v6 cwr bootable to 16GB SanDisc C4 SD using Laptop - Didn't work
Switched to main PC and burned 5.5 to 512mb Nokia C4 SD - didn't work.
Both were attempted with latest Win32DiskImager (.7) from SourceForge.
At this point, I'd lean towards a hardware failure, BUT... it's too coincidental that this occurred during a standard CWR install of a ROM. My understanding is that the Nook is supposed to ALWAYS check the SD slot prior to booting internally. Now whether there is a partition block that tells it to do this or not, I've never dug that far, but I'd have to say that this sure makes it look that way.
If that's the case, then the "unbrickable Nook" (which I once believed to be true) is a fairy tale. The fact that several others around here have met with the same fate, I'm almost inclined to believe it. I'm going to go on a hunt for the original files that fixed my first nook. If only I could remember what the heck I did with them.

Scratch that...
I found the files, but now I have an entirely different issue.
My copy of Win32DiskImager back then was very size specific, and although I have a copy of the 16gb_clockwork file I used back then, I can't burn it because Win32DI says the card isn't the right size..
Ugh... I'll keep you all posted.

majorpay said:
Alright... Well here's where we are at this point:
Bought a Dynex 7 in 1 with specific port for MicroSD - burned v6 cwr bootable to 16GB SanDisc C4 SD using Laptop - Didn't work
Switched to main PC and burned 5.5 to 512mb Nokia C4 SD - didn't work.
Both were attempted with latest Win32DiskImager (.7) from SourceForge.
At this point, I'd lean towards a hardware failure, BUT... it's too coincidental that this occurred during a standard CWR install of a ROM. My understanding is that the Nook is supposed to ALWAYS check the SD slot prior to booting internally. Now whether there is a partition block that tells it to do this or not, I've never dug that far, but I'd have to say that this sure makes it look that way.
If that's the case, then the "unbrickable Nook" (which I once believed to be true) is a fairy tale. The fact that several others around here have met with the same fate, I'm almost inclined to believe it. I'm going to go on a hunt for the original files that fixed my first nook. If only I could remember what the heck I did with them.
Click to expand...
Click to collapse
It is possible that it is a hardware failure of the SD slot. Have you tried cleaning it? The booting to SD is built into the OMAP chip and is not effected by what you have in emmc. It automatically looks at the SD slot first to see if a bootable SD is there. But it looks for specific features of the SD found there to be sure it is bootable. If it is not bootable, it tries the emmc boot partition and if valid boot files are not there, it won't turn on.
Sent from my Nook HD+ running CM10.1 on emmc.

Alright, I ended up flashing the old image I used on my last Nook with the same version of win32diskimager I used back then, and still no signs of life.
Unlike the previous issues I had on my first Nook, this one shows no signs of life. No backlit deep black that you can see in the dark, nothing. So I plugged it into my tower PC and held the power for 10 seconds. The install for the OMAP 36xx processor drivers went through the process, but when done, you could not find it in the device manager. So I held the power again for 10 seconds, it showed up for a second, then went away. I repeated this process several times, and same thing each time.
Just to make sure I wasn't leaping to assumptions, I unplugged it and plugged it back into the PC, and no response. Not until I held the power down for 10 seconds again.
So what can we conclude from this? Well, either it is normal for the Nook to show up for a split second on Windows, or the Nook is powering on, then down almost instantaneously. I'm inclined to believe the latter as ordinarily holding the power down for a few seconds wouldn't *reboot* the device, but instead, it would power it down, or power it up (if it was off). Also, unplugging and replugging it in to the PC should have activated the device driver if it was staying on (assuming that isn't a momentary thing on initial startup).
What's the missing piece of the puzzle? I don't know if it's the same for all the other users that have commented, but I don't have the original cable for this device, so I cannot fast charge. A dead Nook will power on, even if drained, when the fast charge cable is used (I believe?). This is something else I will have to try when I get my hands on my dad's Nook. Is it possible that a trickle charge doesn't work below a certain point?
This was kind of my thoughts back when this first occurred - that perhaps the Nook simply lost juice during the install.
Grasping at straws? Perhaps, but straws are all I'm seeing at this point.

majorpay said:
Alright, I ended up flashing the old image I used on my last Nook with the same version of win32diskimager I used back then, and still no signs of life.
Unlike the previous issues I had on my first Nook, this one shows no signs of life. No backlit deep black that you can see in the dark, nothing. So I plugged it into my tower PC and held the power for 10 seconds. The install for the OMAP 36xx processor drivers went through the process, but when done, you could not find it in the device manager. So I held the power again for 10 seconds, it showed up for a second, then went away. I repeated this process several times, and same thing each time.
Just to make sure I wasn't leaping to assumptions, I unplugged it and plugged it back into the PC, and no response. Not until I held the power down for 10 seconds again.
So what can we conclude from this? Well, either it is normal for the Nook to show up for a split second on Windows, or the Nook is powering on, then down almost instantaneously. I'm inclined to believe the latter as ordinarily holding the power down for a few seconds wouldn't *reboot* the device, but instead, it would power it down, or power it up (if it was off). Also, unplugging and replugging it in to the PC should have activated the device driver if it was staying on (assuming that isn't a momentary thing on initial startup).
What's the missing piece of the puzzle? I don't know if it's the same for all the other users that have commented, but I don't have the original cable for this device, so I cannot fast charge. A dead Nook will power on, even if drained, when the fast charge cable is used (I believe?). This is something else I will have to try when I get my hands on my dad's Nook. Is it possible that a trickle charge doesn't work below a certain point?
This was kind of my thoughts back when this first occurred - that perhaps the Nook simply lost juice during the install.
Grasping at straws? Perhaps, but straws are all I'm seeing at this point.
Click to expand...
Click to collapse
I think what you are seeing is the device powering on with the screen off (like it normally does), looking for boot files in SD and emmc and when seeing none, immediately powering off. That is why the brief driver showing in windows. Ordinarily if it finds those boot files, it turns the screen on and continues the boot.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
I think what you are seeing is the device powering on with the screen off (like it normally does), looking for boot files in SD and emmc and when seeing none, immediately powering off. That is why the brief driver showing in windows. Ordinarily if it finds those boot files, it turns the screen on and continues the boot.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Bit the bullet and grabbed my dads. It's confirmed, the SD card I recently burned works - CWR booted right up. Now for the stock cable test.

Stock cable confirms that the Nook will not power up at all - cable is green indicating full charge. This Nook is toast - so just coincidence that it was during flashing PA? Hard to believe, but haven't I ruled every other possibility out?
EDIT - moved the cable and it turned orange. Coworker confirmed that his Nook charger he was using wouldn't even charge a phone I loaned him. May be on to something here. I'll wait until the cable turns green.

I'm done...
I'm beat. Cable turned green again, and no dice. This Nook is headed for the scrap pile (unless I get a wild hair and tear it apart to re-solder some joints).

majorpay said:
Stock cable confirms that the Nook will not power up at all - cable is green indicating full charge. This Nook is toast - so just coincidence that it was during flashing PA? Hard to believe, but haven't I ruled every other possibility out?
EDIT - moved the cable and it turned orange. Coworker confirmed that his Nook charger he was using wouldn't even charge a phone I loaned him. May be on to something here. I'll wait until the cable turns green.
Click to expand...
Click to collapse
I went back to your OP and re-read. It is very common for an installation to screw up and lock up, leaving the boot partition borked. But usually the user can boot to a bootable CWM and re-flash and it repairs it. Ordinarily I would say that the slot could have been messed up for a long time too, since a lot of users have CWM on emmc and would not know it until they needed a bootable card. But in your case the slot was working right up till after you put CWM on emmc. And your using internal memory to flash the zip from and leaving the SD in the slot is usually of no consequence. But it is remotely possible since you left the SD in and the software was running amouk, that it did something to the SD and the slot, like overcurrents or some such nonsense. I still think the not booting from SD is a slot hardware issue since your card boots on other devices and the booting code is in chip firmware.
Sent from my Nook HD+ running CM10.1 on emmc.

Nook Color dead, nothing working

Hi Everyone,
My nook color is dead - black screen, no matter what I do. I've had it for a couple of years and I rooted it when I first got it. It worked ok, although it seemed like the battery was going dead way faster than it should have. I've tried every solution I could find that looked like it would address my problem, but my device hasn't responded at all. I have wondered if maybe it's the battery, but it doesn't turn on even if I have it plugged in. The little light on the cord will go green when I plug it in.
Any suggestions on what else I can try? I'm pretty close to giving up now. But I really like this device.
Thanks,
Maureen

Dead Nook Color
maurbrown said:
Hi Everyone,
My nook color is dead - black screen, no matter what I do. I've had it for a couple of years and I rooted it when I first got it. It worked ok, although it seemed like the battery was going dead way faster than it should have. I've tried every solution I could find that looked like it would address my problem, but my device hasn't responded at all. I have wondered if maybe it's the battery, but it doesn't turn on even if I have it plugged in. The little light on the cord will go green when I plug it in.
Any suggestions on what else I can try? I'm pretty close to giving up now. But I really like this device.
Thanks,
Maureen
Click to expand...
Click to collapse
Maureen,
I had the same problem and resolved it easily.
1. View the video on how to replace the battery at NewPower99. The video is excellent and describes how to take the Nook apart and replace the battery.
2. Remove the back of the Nook after removing the two screws under the microSD cover. You will need a Torx 5 screwdriver to do this. The screwdriver isn't a very common one, but can be purchased from Sears. And it is not expensive.
3. After removing the back cover, do not remove the ten screws or complete the remainder of the disassembly.
4. The battery connector is the biggest connector on the left side of the Nook (Nook is face down andmicroSD card slot on the right hand side.) It has several red and black wire in the wire harness.
5. The main battery connector is a push on connector, so using a small, flat plastic anything, carefully pry the connector up. The connector has a "rubber bumper" glued to the top of it. Leave the bumper on the connector.
6. After the connector is lifted, leave the battery disconnected for around a half-hour or so.
7. Reattach the power connector by gently placing it over the connector and pushing down.
8. Before reattaching the back, power on the Nook to ensure it will reboot. If it does reboot, push the power button again for a half second or so to get the Nook into the sleep mode. DO NOT POWER OFF. I've done this twice now and learned to only put the Nook to sleep.
9. Replace the Nook rear cover. Don't forget to reinstall the two screws under the microSD cover.
10. Keep the Nook charged if possible. It doesn't have to remain on the charger all the time, but keep enough charge on it so it doesn't turn off.
You will find it is actually VERY easy to accomplish this.
I hope this works for you; it did for me.

maurbrown said:
Hi Everyone,
My nook color is dead - black screen, no matter what I do. I've had it for a couple of years and I rooted it when I first got it. It worked ok, although it seemed like the battery was going dead way faster than it should have. I've tried every solution I could find that looked like it would address my problem, but my device hasn't responded at all. I have wondered if maybe it's the battery, but it doesn't turn on even if I have it plugged in. The little light on the cord will go green when I plug it in.
Any suggestions on what else I can try? I'm pretty close to giving up now. But I really like this device.
Thanks,
Maureen
Click to expand...
Click to collapse
Before you change the battery, see if a bootable SD will boot. You said you tried every solution, but did not mention that. The NC will not turn on unless it finds valid boot files either in internal boot or the SD boot.
Sent from my Galaxy Tab 2 using XDA Premium

ohunter said:
Maureen,
I had the same problem and resolved it easily.
1. View the video on how to replace the battery at NewPower99. The video is excellent and describes how to take the Nook apart and replace the battery.
2. Remove the back of the Nook after removing the two screws under the microSD cover. You will need a Torx 5 screwdriver to do this. The screwdriver isn't a very common one, but can be purchased from Sears. And it is not expensive.
3. After removing the back cover, do not remove the ten screws or complete the remainder of the disassembly.
4. The battery connector is the biggest connector on the left side of the Nook (Nook is face down andmicroSD card slot on the right hand side.) It has several red and black wire in the wire harness.
5. The main battery connector is a push on connector, so using a small, flat plastic anything, carefully pry the connector up. The connector has a "rubber bumper" glued to the top of it. Leave the bumper on the connector.
6. After the connector is lifted, leave the battery disconnected for around a half-hour or so.
7. Reattach the power connector by gently placing it over the connector and pushing down.
8. Before reattaching the back, power on the Nook to ensure it will reboot. If it does reboot, push the power button again for a half second or so to get the Nook into the sleep mode. DO NOT POWER OFF. I've done this twice now and learned to only put the Nook to sleep.
9. Replace the Nook rear cover. Don't forget to reinstall the two screws under the microSD cover.
10. Keep the Nook charged if possible. It doesn't have to remain on the charger all the time, but keep enough charge on it so it doesn't turn off.
You will find it is actually VERY easy to accomplish this.
I hope this works for you; it did for me.
Click to expand...
Click to collapse
Thank you!! I will try to boot from sd once more and then will try this and let you know how it goes.

leapinlar said:
Before you change the battery, see if a bootable SD will boot. You said you tried every solution, but did not mention that. The NC will not turn on unless it finds valid boot files either in internal boot or the SD boot.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Hi! I actually followed some of your links and tried them. I want to try one last time - which of your links should I use? Maybe I did the wrong thing the other times. Thanks a lot.

maurbrown said:
Hi! I actually followed some of your links and tried them. I want to try one last time - which of your links should I use? Maybe I did the wrong thing the other times. Thanks a lot.
Click to expand...
Click to collapse
For making the bootable SD go to my NC Tips thread and see item A9.
Sent from my Galaxy Tab 2 using XDA Premium

leapinlar said:
For making the bootable SD go to my NC Tips thread and see item A9.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Ok! I'm excited to give it a shot. Another question: if it doesn't work, should I try it with a different micro sd just in case it's not formatted properly or the image somehow didn't get on there exactly right? Thanks again.

maurbrown said:
Ok! I'm excited to give it a shot. Another question: if it doesn't work, should I try it with a different micro sd just in case it's not formatted properly or the image somehow didn't get on there exactly right? Thanks again.
Click to expand...
Click to collapse
Yes.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Yes.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Well, I tried the bootable SD and still no response, so then I changed the battery. Nothing. So I think I'm pretty much out of luck at this point. If you can think of anything else to try, please let me know.
Thanks for all the help,
Maureen

maurbrown said:
Hi Everyone,
My nook color is dead - black screen, no matter what I do. I've had it for a couple of years and I rooted it when I first got it. It worked ok, although it seemed like the battery was going dead way faster than it should have. I've tried every solution I could find that looked like it would address my problem, but my device hasn't responded at all. I have wondered if maybe it's the battery, but it doesn't turn on even if I have it plugged in. The little light on the cord will go green when I plug it in.
Any suggestions on what else I can try? I'm pretty close to giving up now. But I really like this device.
Thanks,
Maureen
Click to expand...
Click to collapse
Quite upset, I had just set mine to run CM 10.1 and it was running great. And now I can't get it to start. I think maybe I caused it by tampering with the SD card on the PC and then putting it back in the NC. But even after putting it back as it was (partition inactive so it should boot from emmc as it had done just previous) I get no flash of light when holding in the power button.
Here's the gritty details of what happened with the SD card. I'd made eyeballer's 1gb boot card and enlarged the partition in mini tools to the full 8 gb, and backed up, flashed and updated a few times to emmc. The installation treats the SD card as "/sdcard", so in order to be able to cold boot emmc, I needed the SD card partition to be inactive. Minitools seems to apply the change (no error), but it was failing (partition was still active when retested). Diskpart also failed to reset it. So I backed up the SD card on the PC, reformatted it with SDformatter, and restored the content. As it happened, my PC restore process made it active again. But this time the partition was aligned at 1024, and Diskpart was able to mark it inactive. Used it in the Nookcolor for hours, it was working great. I was able to boot from emmc for both system and recovery. The SD card was serving as "/sdcard". Then I thought I'd like to set up another Nookcolor we have in the family. So I shut mine down, pulled the SD card, and went back to Diskpart and marked it Active. Put it back in my Nook and it failed to light up or start. Made it Inactive again and it still won't light up or start.
It had a nearly full charge before I messed with it. When I plug it in, the charger light is amber.
Sent from my HD+ Running CM 10.1 from emmc

Did you check the cord? Those nookie cords fail all the time u know, not very well made. You should get a new one online.
You use those stock nookie cables, not the custom ones or your nookie will not charge good. =)

Sherip said:
Quite upset, I had just set mine to run CM 10.1 and it was running great. And now I can't get it to start. I think maybe I caused it by tampering with the SD card on the PC and then putting it back in the NC. But even after putting it back as it was (partition inactive so it should boot from emmc as it had done just previous) I get no flash of light when holding in the power button.
Here's the gritty details of what happened with the SD card. I'd made eyeballer's 1gb boot card and enlarged the partition in mini tools to the full 8 gb, and backed up, flashed and updated a few times to emmc. The installation treats the SD card as "/sdcard", so in order to be able to cold boot emmc, I needed the SD card partition to be inactive. Minitools seems to apply the change (no error), but it was failing (partition was still active when retested). Diskpart also failed to reset it. So I backed up the SD card on the PC, reformatted it with SDformatter, and restored the content. As it happened, my PC restore process made it active again. But this time the partition was aligned at 1024, and Diskpart was able to mark it inactive. Used it in the Nookcolor for hours, it was working great. I was able to boot from emmc for both system and recovery. The SD card was serving as "/sdcard". Then I thought I'd like to set up another Nookcolor we have in the family. So I shut mine down, pulled the SD card, and went back to Diskpart and marked it Active. Put it back in my Nook and it failed to light up or start. Made it Inactive again and it still won't light up or start.
It had a nearly full charge before I messed with it. When I plug it in, the charger light is amber.
Sent from my HD+ Running CM 10.1 from emmc
Click to expand...
Click to collapse
The Nook Color is different that the Nook HD/HD+. It is much more temperamental about how the SD is formatted. It must be physically set up just right where the HD/HD+ is more liberal. See my NC Tips thread linked in my signature and look at item A9. You should not be messing with the partition with partition management software, particularly the active/inactive and alignment.
Can you still boot without the SD installed?
I have more information for you but need to know that answer first.
Sent from my Nook HD+ running CM10.1 on emmc.

I sent a long reply earlier and it looks like it didn't post
With no card I got low battery symbol. Plugged it in. Screen stayed black, not used to that, on CM7 it would light up on its own when booted. Pressed the n button, and got the CM 10 lock screen. It was up to 25% then, now its at 53%. Not supposed to run the eyeballer setup without an SD card, so I haven't tried interacting with it.
Sent from my HD+ Running CM 10.1 from emmc

Sherip said:
Not supposed to run the eyeballer setup without an SD card, so I haven't tried interacting with it.
Sent from my HD+ Running CM 10.1 from emmc
Click to expand...
Click to collapse
Why not? Some apps expect an SD to run properly, but there is nothing wrong with running CM10.1 without one.
If your emmc installation runs fine, your problems are because you were messing with that SD. With the NC it is best to make a small SD for your CWM card and put it away and save it for future use. Then use a different SD for use with CM10.1.
With the NC, if you have a bootable SD inserted without valid boot files on it, it turns on, but does not turn the screen on so to you it looks like it is off.
Your solution to your problem is do what I said above, have two SDs. And don't mess with them. You can get away with messing with the SD on a HD/HD+, but not the NC.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Why not? Some apps expect an SD to run properly, but there is nothing wrong with running CM10.1 without one.
If your emmc installation runs fine, your problems are because you were messing with that SD. With the NC it is best to make a small SD for your CWM card and put it away and save it for future use. Then use a different SD for use with CM10.1.
With the NC, if you have a bootable SD inserted without valid boot files on it, it turns on, but does not turn the screen on so to you it looks like it is off.
Your solution to your problem is do what I said above, have two SDs. And don't mess with them. You can get away with messing with the SD on a HD/HD+, but not the NC.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Yes I think working with the HD series nooks made me overly confident yesterday lol
In my missing post I mentioned that it wouldn't boot from my CM7 SD card or a newly burned eyeballer 1gb image yesterday. Before the trouble I had seen my CM7 card boot after CM10.1 was on emmc. Now that the NC is working I'm nervous to shut it down at all or try booting from any SD.
Went out and when I came back the charger was green but the charge percentage said 90%. I switched to a different NC charger. Light stayed green and suddenly it switched from 90% to "charged". On my PC using a card reader, I sdformatted my SD card and did a straight copy paste of the previous folders, leaving off the root files associated with booting, ram disk and such and inserted it in the NC. Disconnected from power. Claimed to be at 100%.
Current readout is 93% and battery time is 28 min 30 sec.
I suppose its possible my battery is going bad. It was chronically plagued with "sleep of death" on CM 7.
I believe I'm running the CM 10.1 nightly of 7/25.
Edit: there are posts that claim you MUST have an SD card inserted to run the eyeballer system. If that's not true I might still need one because I had restored some apps with Titanium and some content had been written there. I think I used apptosd on some of them on sd-based-CM7 in an effort to use my space more efficiently.
Sent from my Nook Color Running CM 10.1 from emmc

Sherip said:
In my missing post I mentioned that it wouldn't boot from my CM7 SD card or a newly burned eyeballer 1gb image yesterday. Before the trouble I had seen my CM7 card boot after CM10.1 was on emmc. Now that the NC is working I'm nervous to shut it down at all or try booting from any SD.
Click to expand...
Click to collapse
My NC is completely back to normal, I've successfully booted using cards that didn't work while I was having trouble. Not sure if it was fixed because I pulled the card to boot emmc as suggested or because the battery got depleted and it went into another state. Either way I'm happy. For now I don't need a torx screwdriver or new battery.
Leapinlar, my eyeballer emmc setup uses an old version of cmw. Its 3.2.0.1. AFAICT it works fine but in other threads I've seen you recommend updated versions. Do you know what changed or improved, and whether my existing backups for stock and CM would be compatible?
Sent from my Nook Color Running CM 10.1 from emmc

Sherip said:
Leapinlar, my eyeballer emmc setup uses an old version of cmw. Its 3.2.0.1. AFAICT it works fine but in other threads I've seen you recommend updated versions. Do you know what changed or improved, and whether my existing backups for stock and CM would be compatible?
Sent from my Nook Color Running CM 10.1 from emmc
Click to expand...
Click to collapse
The 3.2.0.1 is fine. The only real advantage the newer versions have is they allow backup and restore to internal memory. v5.5.0.4 makes and reads compatible backups with 3.2.0.1 if you choose to (3.2.0.1 is img only, 5.5.0.4 is img or tar). v6.0.1.2 makes a new backup format that is not compatible with 3.2.0.1 (tar or blobs). Therefore, I usually recommend 5.5.0.4 so you get internal backups and can read 3.2.0.1 backups.
Sent from my Nook HD+ running CM10.1 on emmc.

[Q] Truly dead Nook Color - possible?

Well, first off let me say I've been researching this issue for about 6 hours, and I've read several hundred posts across dozens upon dozens of threads so, I'll just say I've got a dead NC and I'm wondering if it's truly dead considering how much I keep seeing "it's practically unbrickable..." (which I've heard before on other devices).
Was working fine with 1.4.3 when I got it yesterday (boy that firmware was damned slow, good lord), then I worked out how to get CM7.2 on it and that worked fine for a bit, then I figured I'd give CM10.2 a shot and that worked fine (albeit slow which is seemingly just how the NC is), then even the latest snapshot M7 build of CM11 and even that worked somewhat (constant FC's of gapps, etc, known problems I suppose - yes I did use CWM 6.0.4.8 to install it).
So I did some more research yesterday and found out about MiRaGe CM7.2 being hailed as the best performing ROM for the NC and figured ok this could be just the ticket.
To get CM11 installed I used a Sandisk Class 4 8GB card, the 1gb_clockwork-3.2.0.1-eyeballer image, the snapshot M7 build of CM11, the most current gapps for KitKat (20140606) and then CWM 6.0.4.8, data/factory reset, reboot, worked fine until I decided to get MiRaGe CM7.2 on it.
To install MiRaGe CM7.2, I used the same SD card (the Sandisk), only placed the MiRaGe zip and the gapps-gb-20110828-signed.zip file on the card. Booted the NC to the recovery (CWM 6.0.4.8) and then inserted the SD card, chose to install zip from SD card, browsed for the MiRaGe zip and then started the install - it got to roughly 80% or so and then just hung there for several minutes, then the NC powered itself off and back on again, getting to the Cyanoboot screen, then a flash, then nothing but the display and backlight were obviously on.
Ok, not good, so then I held the power button till it shut off, ejected the card, started it up again, went into CWM 6.0.4.8 again (it was installed to the eMMC), put the SD card back in, factory wipe/etc, install zip, same thing: hung at 80% for a minute or so, then an NC reboot.
It did that twice, and after the third time when I shut it off thinking ok I'll just try the plain old vanilla CM7.2, I pulled the SD card out, put it in the laptop, copied over the CM7.2 zip, popped out the card, back in the NC (but not inserted since I needed to get Cyanoboot up to hold N to get recovery.
That's when the NC wouldn't power back up. Dead, nothing, no response of any kind. Plugged in the charger (factory charger and cable), got the typical colored light (orange or amber or whatever the hell color it is) - before I started this process the NC was 95% for battery, it wasn't plugged in during the attempts to get MiRaGe CM7.2 on it, however.
But even so, no response whatsoever. I held power for 15 seconds or so, pushed in the SD card to try and boot from that, same thing: no response of any kind whatsoever. Popped the card out completely, then decided to try Power+N (nothing), Power for 30 seconds, then let go, power for 5, no go, nothing.
Decided to plug the NC into the computer direct using the factory cable, no response of any kind - the computer is not recognizing anything whatsoever (I know some folks report they get a hardware detection of the OMAP device, I'm not that lucky). Unplug it, hold power for 15 seconds, let it go, wait 10 seconds, plug in the USB cable, still no response, no sound, no activity, no backlight, nada, zip, zilch, zero, null and void, "It's dead, Jim..."
But, I kept trying, using 2 other SD cards I have (a 1GB Sandisk and a 2GB Sandisk), same results: totally dead nothing.
Decided to make this post just for the hell of it but I'm fairly confident that it truly is totally toasted dead. I've tried different CWM bootable images from leapinlar and others, still nothing, no response of any kind, no activity.
I kinda figured that it's truly totally absolutely dead when I plugged it into the laptop and it wasn't detected at all. Holding Power+N while plugging it in (a trick of sheer physical ambidexterity, I assure you) has no effect. Not sure what I may have done, maybe the eMMC is just totally hosed - but then again, it won't boot from SD card either. I've read many posts that say if the boot partition on the eMMC is hosed, it's a dead device but then someone else will say that doesn't matter 'cause you can just put in an SD card (which has boot priority) and it'll fire up but that's not happening with mine.
Went from working device to brick, and I don't know how unless something just totally died in the process that shouldn't have. Oh well, I only paid $25 for it from someone that just didn't use it anymore. Did require a 45 minute charge to get it to wake up yesterday when I got it - previous owner said it had been in a drawer for like 9 months, hadn't been touched at all and I figured it was cheap and would give me something to do.
I know it's dead but, there's always some hope... right?

How you got to your problem was using that 6048 to try to flash mirage. You must use a version of CWM older than 6045 for it to successfully flash older zips. It now sounds like your battery is depleted. That is why you do not get the OMAP thing. Many have successfully revived their devices by dismantling and temporarily disconnecting the battery. I recommend trying that. Then it may boot to one of my older bootable CWM SDs.
Sent from my SCH-i705 using XDA Premium HD app

Well I'll be damned... IT'S ALIVE!!! (MUAHAHA--errr... you get the point).
Lifted up the back panel enough to disconnect the battery for a few minutes (don't have a Torx T-5 around here it seems, now I have reason to get one), and sure enough as soon as I reconnected it the NC sprang back to life, so that's pretty awesome. Thanks, I had thought of doing that earlier and figured it might not make that much of a difference, apparently that was a mistake that has now been corrected.
Pushed MiRaGe CM7.2 + Gapps to the device, and I have to agree with everything that's been said so far: right from the gitgo it's fast, faster than anything else I've put on here so far and I suppose given the age of the device, this is pretty much the best it's ever going to be capable of.
I wish KitKat could get a nice clean rebuild leaving out a lot of the cruft for a nice lean install on the NC, some aspects of that version of Android are very cool and the fact that it's designed from the ground up to work better with older hardware aka "limited resource devices" with low internal RAM would sure make it seem like just what the NC really needs.
Oh well, at least it's functional again, thanks for the suggestion, leapinlar, as always your assistance is greatly appreciated.