Database Develop

BRICKED:No power on, no boot from SD

I was running froyo off of eMMC with the OCed kernel at 1.1ghz.
Replaced the SD card with another and although clockwork was already installed I used rom manager to install it again before selecting reboot to recovery to make backup. I did this because I thought it might need to have some temporary files on the SD card in order to reboot into recovery from within rom manager.
It turned off.
Since then I have tried holding the power button for 20 seconds, holding it while holding the 'nook' button, booting off of SD card, holding ALL the nooks buttons, everything.
The screen will not turn on and it is fully charged.
If I'm not able to fix it soon I'm going to take it back to B&N.
Any other ideas?

When you plug in your nook to your computer what happens?

Download clockwork uSD boot, as well as a stock ROM (preferably stock barnes & noble), and while the unit is off hold down the "n" and press and hold the power button... then re-install

I've tried a bootable clockwork SD card as well, and plugging it into the computer. The only thing that changes is the charging light.

devin.slick said:
I've tried a bootable clockwork SD card as well, and plugging it into the computer. The only thing that changes is the charging light.
Click to expand...
Click to collapse
Other than error in burning an SD card it seems like you burnt out your processor. The 1.1GHz runs at slightly higher voltages which could've caused this

same story here except i was not running overclocked, nothing turns on, any ideas

I don't know you probably tried this but i held my power button for like thirty seconds or so which is like a cold shutdown. Then try powering on like normal worked for me

devin.slick said:
I was running froyo off of eMMC with the OCed kernel at 1.1ghz.
Replaced the SD card with another and although clockwork was already installed I used rom manager to install it again before selecting reboot to recovery to make backup. I did this because I thought it might need to have some temporary files on the SD card in order to reboot into recovery from within rom manager.
It turned off.
Since then I have tried holding the power button for 20 seconds, holding it while holding the 'nook' button, booting off of SD card, holding ALL the nooks buttons, everything.
The screen will not turn on and it is fully charged.
If I'm not able to fix it soon I'm going to take it back to B&N.
Any other ideas?
Click to expand...
Click to collapse
I just got done with a similar, most frustrating experience.
1) Was on stock B&N 1.0.1... then updated to 1.1.0 --- Everything worked fine
2) Then ran autonooter 3.0 --- installed but could not get Market to work
3) Ran autonooter 3.0 again --- this time Market worked
4) Installed the OC kernel --- started seeing random locks
5) Decided to go CWR and reflash stock --- boot loop back into CWR
6) Formatted /system and /data under "mounts"
7) Accidentally formatted boot --- Oh man, the headache began
From here on out, my NC would not boot.
1) Tried power + n --- nothing
2) Tried holding power for 20 seconds --- nothing
3) Burned Nook Froyo 0.59 SD --- nothing
4) Burned Nook Froyo 0.58 SD --- nothing
5) Burned iMonster's image of bootable CWR --- nothing
6) Decided to hold power down with bootable CWR --- finally boot in CWR
7) Got another SD and copied stock 1.0.1 zip image (found on the forum)
8) Insert SD card and did an "install from SD card"
Finally... it loaded and boot back into stock. Lesson for the day, don't be too quick to press the home button when in CWR, as you might select a wrong action... then you are screwed. Yes... I even scrolled down to the "Yes"... as I wasn't paying attention. Man.... this wasted literally 3 hours of my life. After it stopped booting... was where most of the stress came in...

hvuong2 said:
I just got done with a similar, most frustrating experience.
1) Was on stock B&N 1.0.1... then updated to 1.1.0 --- Everything worked fine
2) Then ran autonooter 3.0 --- installed but could not get Market to work
3) Ran autonooter 3.0 again --- this time Market worked
4) Installed the OC kernel --- started seeing random locks
5) Decided to go CWR and reflash stock --- boot loop back into CWR
6) Formatted /system and /data under "mounts"
7) Accidentally formatted boot --- Oh man, the headache began
From here on out, my NC would not boot.
1) Tried power + n --- nothing
2) Tried holding power for 20 seconds --- nothing
3) Burned Nook Froyo 0.59 SD --- nothing
4) Burned Nook Froyo 0.58 SD --- nothing
5) Burned iMonster's image of bootable CWR --- nothing
6) Decided to hold power down with bootable CWR --- finally boot in CWR
7) Got another SD and copied stock 1.0.1 zip image (found on the forum)
8) Insert SD card and did an "install from SD card"
Finally... it loaded and boot back into stock. Lesson for the day, don't be too quick to press the home button when in CWR, as you might select a wrong action... then you are screwed. Yes... I even scrolled down to the "Yes"... as I wasn't paying attention. Man.... this wasted literally 3 hours of my life. After it stopped booting... was where most of the stress came in...
Click to expand...
Click to collapse
Here's my experience so far, been trying to unbrick my device:
1) Was on stock B&N 1.0.0... then updated to 1.0.1 --- Everything worked fine
2) Used auto-nooter --- got everything to work fine
3) Ran Honeycomb image v4 --- worked
4) Manually installed su --- root worked
5) Applied OC to 1.1Ghz --- worked, then somehow the device booted back to Eclair eMMC
From here on out, my NC would not boot, it doesn't pass the "Touch the future of reading" screen.
1) Tried power + n --- nothing
2) Tried holding power for 20 seconds or till device shuts --- nothing, even for 2-3 cycles of 8 failed resets
3) Burned Nook Froyo 0.67 SD --- nothing
4) Burned Nook Froyo 0.58 SD --- nothing
5) Re-burned HC v4 SD ---nothing
6) Burned iMonster's image of bootable CWR 128mb --- nothing
7) Burned iMonster's image of bootable CWR 1gb --- nothing
8) Tried to hold power down with bootable CWR --- also nothing
9) Tried to burn a Nooter SD, tried SSH tunneling to 192.168.2.2 --- both Windows and Ubuntu clients do not detect
So at this point, I can't even get into bootable CWR, after the screen where the 'LOADING' word is between 2 skulls (the irony haha), the screen remains black (the LCD backlit is switched off).
Anyone in the same shoes as I am, and have found any workarounds, suggestions? Greatly appreciated!

tucci999 said:
same story here except i was not running overclocked, nothing turns on, any ideas
Click to expand...
Click to collapse
I had this issue too, but it seems I left the autonooter sd card in the slot which prevents booting untill you remove it.
migrax

If you cannot reach it from an ADB shell you *may* be hosed. There's a chance it is actually running and hard-locked in which case waiting for the battery to completely discharge may allow a true cold-boot.
Do some searching in the forums for "nook brick" and you will find several other techniques that have worked for others. Short of frying your CPU, these things really seem pretty bullet proof...
Good Luck.

I was literally in the same exact position as you maybe 2-3 hours ago. Thought I bricked my NC as well. Here's what I did to get past everything:
1) Downloaded the 128mb bootable CWR Burned it to a 2GB card using Win32DiskImager. (legacyschool.us.to/nookdev/clockwork/cwm_128mb.tar.gz)
(Credit: thecubed)
2) Burned it to a 2GB card using Win32DiskImager.
3) Put the card in, held the power button for ~60 seconds. The first time I did this, it worked. I got the two skulls with "loading" in between them. The second time I tried this, (I did it again to verify I knew what the solution was.) I held the power button for a minute again. This time nothing happened. So I just repeated the process. About 20-30 seconds into the second hold, it worked.
4) Download the stock 1.0.1 firmware. (etoile-laconnex.com/nook-complete-restore-1.0.1.zip)
(Credit: samuelhalff)
5) Drag the .zip onto another sd card. Don't burn it.
6) Remove the card from the NC. -> Insert the one with the stock firmware on it.
7) In CWR, go to install from sd. Find the .zip
8) Reboot into stock 1.0.1 firmware.
That's how I got out of it twice. The biggest thing was pressing the power button for a while, even multiple times.

This last option could work. If not, do the same (flash in CWR) but with the boot repair zip files found on my froyo on emmc thread.
Don't panic. Very little chance your NC is bricked..
Sam
Sent from my HTC Desire using XDA App

Hi guys, thanks. I've added these to my attempts, without any improved results:
Retried:
1) Tried power + n (nothing, stuck at 'Touch the Future of Reading')
2) Tried holding power for 20 seconds or till device shuts (nothing, even for 2-3 cycles of 8 failed resets)
3) Burned Nook Froyo 0.67 SD (nothing, 'LOADING' word seen, then LCD shuts)
4) Burned Nook Froyo 0.58 SD (nothing, 'LOADING' word seen, then LCD shuts)
5) Re-burned HC v4 SD (nothing, 'LOADING' word seen, then LCD shuts)
6) Burned IOMonster's image of bootable CWR 128mb (nothing, 'LOADING' between 2 skulls seen, then LCD shuts off)
7) Burned IOMonster's image of bootable CWR 1gb (also nothing, same as above)
8) Tried to hold power down with bootable CWR (nothing)
9) Tried to burn a Nooter SD, tried SSH tunneling to 192.168.2.2 (nothing, Win7 and Ubuntu clients do not detect)
New:
10) Using CMR 128mb/1gb again (via Win32DiskImager and WinImage)
a) tried booting it by switching device via connection to USB (nothing, 'LOADING' fades to black)
b) tried holding power > 60 to 120 seconds (nothing, same as above)
c) tried holding power + n > 60 to 120 seconds (nothing, same as above)
d) tried holding power + n, wait ~60 seconds, released n but still holding power ('LOADING' doesn't fade and nothing happens)
So at this point:
1) At any time, the PC doesn't detect any hardware changes for adb to work / re-installation of drivers
2) Linux doesn't detect too
3) I feel as if I've exhausted all methods to reinstall back to stock
4) CWR on eMMC is still there, I still can't get into bootable CWR
All I need to do now is wait for a full battery discharge, for the true cold boot option (thanks ColoradoPhoney). Also, thanks everyone.

Rawfish: Maybe try a different uSD card? I've had them fail at crucial times in the past. Just a thought.

Did you completely reformat your sd card or try a different one? I had problems with booting from one of my sd cards.

Leatha & knappy, tried on 2. One's a 256mb sandisk, another a Transcend 8gb class 6. will go get a 2gb and/or 4gb ones today. Thanks for the suggestions.

LeathaLurker said:
Did you completely reformat your sd card or try a different one? I had problems with booting from one of my sd cards.
Click to expand...
Click to collapse
On top of this, I would actually recommend using Partition Master on one of the cards, do a completed delete of all partitions, create a new single win32 partition, format, then image the bootable CWR image onto the card.
The key was to hold down the power button. Yes... it's very frustrating... especially if it happens multiple times. But it's all part of the learning curve... (the not so fun part).

Bought a 2GB uSD and 4GB uSDHC (both Sandisk) today (they tend to have better compatibility and performance, plus they are sold at BN's website under Accessories too). Still no go (also used a new card reader).
Tried using Partition Master too, with no results. Have fully charge device, none response too.
So the solution still remains elusive. Simply cannot boot into CWR SD or any other roms on SD. Tried all methods here to no avail - with focus on Sam's Restore to Stock and thecubed's CWR SD's methods.

I had a similar problem last night... I flashed nookie froyo 0.6.7 and everything seemed to be working fine, I flashed CWR and wanted to flash a new kernel, so I hit reboot into recovery and everything died, I was tired as hell so I just put it aside and figured I'd deal with it in the morning.
Well nothing would get it to turn on, but eventually I got it to turn on by holding N + Power for 20 seconds, and booted to the SD card. I tried restoring my nandroid backup of Rooted 1.1, but it fails to boot when I restart. I can pretty much get into CWR to flash anything, but it fails to boot afterwards. Any ideas?
Also, my rom history went like this:
Stock 1.0.1 > Rooted 1.0.1 > Rooted 1.1 > Honeycomb v4 eMMC > Rooted 1.1(nandroid) > NF 0.6.7

[Q] Is my Nook Bricked beyond all hope

I was reading this thread [RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!). But, since I am new to this forum I couldn't post there. I hope this is the right place to ask for help.
I upgraded my NC to 1.1.0 successfully. I put Autonooter 3.0.0 on a MicroSD card. With my NC off, I inserted the card and then plugged the NC into my PC. I got a black screen for over 5 minutes. It looked like nothing was happening, so, I disconnected the NC, removed the SD card and tired to turn the NC on. No joy, it won't turn on and won't boot at all. I think my Nook is bricked. Any ideas what went wrong?
I've read some other threads about similar problems. It seems there is a fix to get it back to stock (1.1.0). I hope the Recovery thread I mentioned above is where the answer lies. But, I'm a bit confused and don't want to make any more mistakes. I only have one 4GB SD card at my disposal right now.
My questions are as follows:
1. Is my NC bricked beyond hope of recovery?
2. If I follow the procedures in this post can I get it to boot from the sd card even though it won't turn on at all?
3. What is the difference between the Rootpack and the Clockwork Recovery Image?
4. This is the confusing part. Should I download the RootPack? Or, should I download a bootable Clockwork SD card (128mb, 1gb, 2gb, 4gb, 8gb)
5. Since I only have a 4GB card, what should I choose?
6. Should I opt for 1.0.1, or 1.1.0 where it was still working.
7. Can I get all of this on one 4GB card?
8. Is there anything else I should be weary of before starting this procedure?
If i have posted this in the wrong place, I am sorry. But, I hope someone can clear things up for me. Thanks.

This is the right place to ask general questions.
1. Most certainly not.
2. Yes, using a bootable CWR SD is the way to go.
3. Totally different. The Rootpack is the name given to a package that helps you root your Nook. CWR image is a recovery image. That means you can boot to this recovery utility and apply changes to you NC (like repairing stuff, making backups, etc.).
4. An image will adapt to the drive. If you have a 4GB SD and burn (dd) a 1GB image to it, your SD will suddenly present itself as a 1GB SD. If you format it with the right tool, your SD will be 4GB again. So don't panick, if it says 1GB after burning, it's jut "adapted to the image". You haven't lost any disk space.
5. 1GB would be enough, but you can go up to 4GB image with a 4GB.. It could sometimes be a problem to apply an image which is the exact same size as the drive. I would use th 1GB, which is plenty for what you are going to do.
6. That's up to you. Both should work.
7. Yes.
8. Just read threads exhaustively before attempting anything..
So what you need to do is read threads about this CWR Bootable img to learn how to burn it to your SD.
Then, find the appropriate .zip files to flash (apply) (1.1 recovery and 1.0.1 are available in dev section.
Copy them to root of SD.
Boot with the SD Card and apply zip files from SD.
If your NC should still have problems booting, you can also apply a boot repair zip file, that you will find on my Nook Color restore to stock tread in dev..
Sam

His Rootpack wont work on 1.1.0 You should have seen that in his instructions. It will only block 1.1.0 and fake it. You need to see this thread to fix your nook. It is 100% NOT bricked, just messed up atm. You can fix it tho. Read here:
http://forum.xda-developers.com/showthread.php?t=949699

Thanks for thr quick reponse Sam. I'm at work now, but will be able to use your suggestions later this afternoon\tonight. So, if I get a 1gb CWR image on my 4gb sd card, plus the 1.1.0 zip file and put it in the root of the sd card, the Nook should boot up even though I can't turn it on now? How long typacally will it take to boot up? What should I expect to see?
I will post results after I try the procedure. Thanks again!!

Thanks Thiboi69. I have printed out the instructions from the link you sent and will follow them to the T. I'll post results later.

It will work. I have never heard of a 100%bricked NookColor to date. And I have read 1,000's of posts here over the past 4 months. IT is just your boot partition that is messed up and B&N made it check the sdcard first for a Boot partition, then fall back to eMMC. Thank you B&N !!!

I downloaded all the files, wrote them to my sd card, and put it in the Nook. When I connected the Nook to my pc, I got a messaage the the battery was too low to turn on. So, I took the sd card out, and put the Nook on charge. After a while, it turned on, booted up and when I checked my OS, I found that I had
version 1.1.0. Apparently, my attempt to root with autonooter 3, never got installed, partially or completely. And, my battery probably got to low to turn the nook on. So, I didn't need to use CWR after all. I apologize to all who have tried to help me. But, all replies were good and contained useful info.
Now, my question is: Should I try to use Autonooter 3 again, or is there an easier
(more foolproof) way to root v1.1.0?

I just got a nook last night with the sole intention of hacking it - and did so in a matter of minutes. Autonooter couldnt be easier! When you get to the part of putting the SD card in the nook and connecting it to USB to make it boot, just plug it in and go get a cup of coffee. Don't unplug or touch anything until it boots up by itself. At 1st I thought it wasn't doing anything as I didn't see a clockwork mod screen come up or anything, but just be patient and it'll tell you when it's done. Just make sure it's pretty well charged when you do it - mine was about 80% or so.
Honestly after less than a day of the rooted stock 2.1 Eclair OS, I'm ready to drop a fully customized Froyo or Gingerbread image on this thing. Autonooter it 1st and run it for a few days 1st and see what you think. I'm still learning the ins and outs of tinkering with this thing, but so far it seems much easier than the Epic and Moment I've been beating on. Seems pretty well unbrickable too thanks to the boot to SD 1st option B&N baked into this puppy.

jostarr said:
I was reading this thread [RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!). But, since I am new to this forum I couldn't post there. I hope this is the right place to ask for help.
I upgraded my NC to 1.1.0 successfully. I put Autonooter 3.0.0 on a MicroSD card. With my NC off, I inserted the card and then plugged the NC into my PC. I got a black screen for over 5 minutes. It looked like nothing was happening, so, I disconnected the NC, removed the SD card and tired to turn the NC on. No joy, it won't turn on and won't boot at all. I think my Nook is bricked. Any ideas what went wrong?
I've read some other threads about similar problems. It seems there is a fix to get it back to stock (1.1.0). I hope the Recovery thread I mentioned above is where the answer lies. But, I'm a bit confused and don't want to make any more mistakes. I only have one 4GB SD card at my disposal right now.
My questions are as follows:
1. Is my NC bricked beyond hope of recovery?
2. If I follow the procedures in this post can I get it to boot from the sd card even though it won't turn on at all?
3. What is the difference between the Rootpack and the Clockwork Recovery Image?
4. This is the confusing part. Should I download the RootPack? Or, should I download a bootable Clockwork SD card (128mb, 1gb, 2gb, 4gb, 8gb)
5. Since I only have a 4GB card, what should I choose?
6. Should I opt for 1.0.1, or 1.1.0 where it was still working.
7. Can I get all of this on one 4GB card?
8. Is there anything else I should be weary of before starting this procedure?
If i have posted this in the wrong place, I am sorry. But, I hope someone can clear things up for me. Thanks.
Click to expand...
Click to collapse
Joe, I would recommend downloading the 1gb rootpack image and a restore to stock file. Make your bootable clockwork recovery image, place the resotre to stock file on the sdcard, turn your nook off, insert the sdcard, power on and flash the file. All this info and more can be found in my thread here:
http://forum.xda-developers.com/showthread.php?t=949699

Thanks for your suggestion Riley, please take a look at my post # 7 above. Seemd my NC
had a low battery. When I charged it, all was ok. It booted up and I was back in 1.1.0.
But, I just now tried autonooter 3.0.0 again. When I pluged thr NC inyo my PC, I got some sort or warning message. I hit cancel and waited a few minutes. The message came up again. It said the device was not recognized. I unplugged, removed the card, and my fully charged NV won't turn on. And, windows explorer can not read the sd card. This is basically what happened yesterday to cause my panic. The sd card had all the files befor I inserted it into the NC. Now, it's unreadable and I can't turn on or boot the NC again.
Is it autonooter 3.0.0, or the card, or the Nook, or me?????

One correction to post # 10. I can read the sd card in windows explorer. But my NC won't turn on.

With sd card out of the Nook, I get a "Welcome to the Found New Hardware Wizzard"
What does this tell anyone about the condition of my Nook?

I am having a problem and don't really know what to do. When I start my NC its stops at the N screen and goes no further. I've tried a lot of the different ways to get it back to stock with no luck. When I try to write CWM to my SD card with win32 it either doesn't have enough room to put the stock file on the zip with it or when I open the SD card it says the card needs to be formatted. The file is a tr.gz or something like that is there a step between that I am missing or just download the CWM and write to SD using win32? I also tried adb with no luck. I am very new to rooting so any super dumbed down instructions would be greatly appreciated.
Sent from my ADR6300 using XDA App

You can put the rom image to a separate SD card. Just swap it after you boot up from cwr. I did it before for flashing froyo to emmc.
Sent from my PC36100 using XDA App

72chevy2k2 said:
I am having a problem and don't really know what to do. When I start my NC its stops at the N screen and goes no further. I've tried a lot of the different ways to get it back to stock with no luck. When I try to write CWM to my SD card with win32 it either doesn't have enough room to put the stock file on the zip with it or when I open the SD card it says the card needs to be formatted. The file is a tr.gz or something like that is there a step between that I am missing or just download the CWM and write to SD using win32? I also tried adb with no luck. I am very new to rooting so any super dumbed down instructions would be greatly appreciated.
Click to expand...
Click to collapse
Have you followed the restore-to-stock procedure outlined in this thread?
http://forum.xda-developers.com/showthread.php?t=914690

Just a noobish advise!
After configure everything and become accustomed to some of the NC behaviors this should not matter, but I remember at my first attempts at rooting the NC, using a Win7 PC was much easier than using Win XP or iOS devices. Might fix your 'not recognized' problems, sd card recognition and formatting problems etc.

It has CWM on it. I can get it to recovery but it will not recognize the SD or not mount it and I go to mount it in the menu and it says something like can not mount SD card so I have been trying to do the CWM SD burn but I keep getting the above errors I am on a vista computer so I will try it on my windows 7 one and see how that goes. And the different SD card one I will try that as well after work thank you for the help.
Sent from my ADR6300 using XDA App

RickOSidhe said:
Have you followed the restore-to-stock procedure outlined in this thread?
http://forum.xda-developers.com/showthread.php?t=914690
Click to expand...
Click to collapse
Yes I did try that one I put the nookie froyo on the SD and put it I'm my turned off NC and plugged it in to my computer and it sat at the N screen forever and after a while I took it off and it was still in the same state could the CWM be the problem?
Sent from my ADR6300 using XDA App

I'm not sure what posts 13 thru 18 have to do with my problem???

Just didn't feel like starting a new thread for the couple of questions I had along the same line as yours.
Sent from my ADR6300 using XDA App

[Q] Nook won't turn on.

So I did what I wasn't supposed to do: I rooted my Nook and decided I wanted CM7. So I went into CWR, rom zip in hand, and that's when the trouble started. My plan was to format everything, so I started with boot. CWR froze and it hasn't turned on since.
Now, I've searched and read everything about this exact situation. I need a bootable CWR sdcard and then flash the repartition boot zip.
That would be great except every CWR sdcard I burn, never works. Nothing can get this thing to come to life. I burn the sdcard, put it in the Nook, plug it to the PC and nothing happens.
I have a 2GB and 16GB card, and I've tried the 2GB images, 8GB images, 128 MB images, everything.
I really don't know what is going on, but I believe I have the world's first bricked Nook.

spellrm said:
So I did what I wasn't supposed to do: I rooted my Nook and decided I wanted CM7. So I went into CWR, rom zip in hand, and that's when the trouble started. My plan was to format everything, so I started with boot. CWR froze and it hasn't turned on since.
Now, I've searched and read everything about this exact situation. I need a bootable CWR sdcard and then flash the repartition boot zip.
That would be great except every CWR sdcard I burn, never works. Nothing can get this thing to come to life. I burn the sdcard, put it in the Nook, plug it to the PC and nothing happens.
I have a 2GB and 16GB card, and I've tried the 2GB images, 8GB images, 128 MB images, everything.
I really don't know what is going on, but I believe I have the world's first bricked Nook.
Click to expand...
Click to collapse
I had similar problems early on. Found out app i used wasnt burning image. Try older version of win32 disk imager. If the burn is bad, nook wont power on till sd card is removed.

Nook might really be dead - HELP!

I am helping a friend with his Nook, and i've run out of options for fixing it. I have gone through every help thread here, tried things I've found on other forums; no love. I'm hoping someone can review the situation and maybe point me in another direction.
I don't have the exact history on this Nook. I believe that when it was last working it had an early ICS (full-o-bugs) ROM installed on the eMMC. It's definitely been rooted/rom'd/cwm'd in its life.
Here's the status:
--The battery is working and will charge to "green" status. Leaving it unplugged for a few days then plugging it back in will result in "orange" charging back to "green".
--There is no visible indication that the Nook is turning on. Holding the power button for a few seconds up till a few minutes never engages the screen backlight, or any other sign of startup. Same goes for holding "N" with power, holding either/both volume buttons with power.
--If I plug the Nook into a PC, the PC's device manager shows a device connecting (OM??? or something) for maybe one second, then drops off immediately. Unplugging/plugging after that will result in no connection attempt. However, if I unplug, then hold the power button for around 10 seconds, then plug back it, it will attempt the brief connection again. Same goes for just holding the power button down while it is connected, after around 10 seconds you'll see it connect and immediately drop.
--The above situation occurs with the SD card removed, or with a "boot imaged" SD card installed. I'm using a 2GB card that has been setup using Win32 Diskmaker and the ISO downloaded from the Help thread here. I believe it has CWM 3.0.2.8 on it.
--Have opened the back cover and disconnected the battery for as long as a day, no effect.
My assessment here is that the device is still functional, but it is unable to boot. Or whatever it is booting to is immediately locking it up. I really appreciate any guidance here; I hope I can help my friend get his Nook running as beautifully as my Phiremodded one is!

bluevolume said:
My assessment here is that the device is still functional, but it is unable to boot. Or whatever it is booting to is immediately locking it up. I really appreciate any guidance here; I hope I can help my friend get his Nook running as beautifully as my Phiremodded one is!
Click to expand...
Click to collapse
The first step I think I'd take here is to create a working bootable SD card with CM7 on.
Follow the verygreen method and use the latest CM7 from the MiRaGe thread.
http://forum.xda-developers.com/showthread.php?t=1000957
http://forum.xda-developers.com/showthread.php?t=1344873
Use win32diskimager to create the original SD card from the verygreen img file and use a real USB card reader not a slot on a PC. Using other methods can result in cards that won't boot.
You can do all these steps on your Nook without endangering or changing its contents because all this is doing is creating a bootable SD card with CM7 on that you can check on your Nook.
Once you have that working just put the Sd card in your friend's Nook and it should just work.
Having proved that you can then choose what to do next. E.g. You could repeat the process but create an SD card that will load a ROM to the internal emmc memory using the Eyeballer method. If you do that DON'T put it in your Nook as it will change yours.

If I read this carefully enough...you are booting to a black screen, right? In many cases the nook is working but the back light isn't coming on, sometimes because of an erased partition. If you still have an intact ROM partition in the emmc, then you can do the 8x failed reboot, and it will return to out-of-the-box stock.
It can be a little tricky w/o a screen, but hold down the power, n, and both volume keys for 8-10 seconds. The nook will turn off and restart (I believe it restarts, if not do it manually, this is from the top of my head) as soon as it starts booting (1-2 secs) do it again for a total of 8 times. If you let it run too long the process will have to be repeated, so if it doesn't work the first time, try the entire process again.
If it works, it will restore the read-only-memory partition that holds the b&n factory firmware. To be safe, login to the b&n registration, go into settings and do a factory wipe from within the settings. Then you can restore a backup or start over.
If this doesn't work, then you may have wiped your ROM partition, which requires a little more aanced work. Post if it doesn't work and I may be able to help if neither the bootable sdcard or reset methods fix it.

Update: I tried the 8 failed boots thing and wasn't able to get any response from the Nook. It's kinda difficult to know if you're doing it right though when nothing ever lights up on the Nook.
I tested the SD card on my Nook (the functional one), and it does work. The bootloader had the little skull and crossbones guys, and then it loaded up CWM.

bluevolume said:
Update: I tried the 8 failed boots thing and wasn't able to get any response from the Nook. It's kinda difficult to know if you're doing it right though when nothing ever lights up on the Nook.
I tested the SD card on my Nook (the functional one), and it does work. The bootloader had the little skull and crossbones guys, and then it loaded up CWM.
Click to expand...
Click to collapse
So the SD card from your friend's Nook which doesn't do anything in his machine will bring up CWM in yours?
I think this could mean one of two things. The SD card may be booting through to a CWM install on your emmc and therefore when used in his machine with a screwed up emmc then it doesn't work. Or there is some dependency on the emmc which is also allowing it to work in your machine but not his. I'm not sure what these dependencies are but I could see that if it was a full OS like CM7 then it may need a working emmc ROM partition at least, but CWM I thought was pretty much independent when run from the SD.
I still think your best initial bet is to prepare a new SD card on your machine with even a basic eyeballer CWM boot. Prove it works on your machine and then try it on your friend's. That at least proves that it is functioning hardware wise and booting as normal of the SD.

Well
You could take it to B&N even though the warranty was voided

[Q] Internal storage and ext sd wont read.

Ok first off I have read through a lot of different forums from here and different websites. Could not find a solution.
MY cappy was rooted and I was running cm9 on it for a while working great.. decided to give cm 10.1 a try. Well it worked for about 2 1/2 months. doing the updates that came out every day. Then the other I was playing a game on it. I stoped the game unplugged the phone from the wall charger went outside to smoke and went to check the phone. It was a black screen where it was semi light up though.
I of course tried hitting the power about 15 times no response. So I took out the battery and put it back in. It rebooted into recovery. So I hit reboot phone. Went back into recovery. Went in cleared cache and dalvik cache rebooted. Went back into recovery, so from there I went to install zip from sd card. there was nothing on sd card.
I then put it into download mode and using odin I brought it back to stock 2.3.4 after odin had suceeded it installed everything on phone. But it came with error no internal storage found. It booted fully. So then I tried heimdall one click it then did the same thing I cleared cache and did a factory reset. IT rebooted fully.
It only works when I have my ext. SD card in the phone though. If i pull my ext sd card out it will go into a boot loop. IF i put my ext sd card into another phone and back to my cappy Itll stay in boot loop. I have formatted sd card put it back into the phone and rebooted. and same thing. bootloop. So I then have to go through the process again to get it semi running. It wont read ext or internal sd card when phone is fully on.
So is there any way to get it to read internal storage again? Or even ext. I dont understand why it will run with the ext.
Any help will be appreciated Thank you.

No one has any answers to this?

bubba1993 said:
No one has any answers to this?
Click to expand...
Click to collapse
Your issue is kinda odd, the only thing I can think of is the EU bug but that's on ICS and you said you were on JB. Either way, could be worth looking into, there's a thread for it in here.

BWolf56 said:
Your issue is kinda odd, the only thing I can think of is the EU bug but that's on ICS and you said you were on JB. Either way, could be worth looking into, there's a thread for it in here.
Click to expand...
Click to collapse
Well I was on cm 9 then went to cm 10.1 4.2 I have no clue I looked into the EU bug tried to fix it no luck. I can put the sd card on it and flash the stock rom and kernel and it will run just without it reading internal or external sd card

the external sd card has probably got your .androidsecure hidden folder on it, possibly more. if your phone had the eu bug, then CM10 recognizes that and switches the mounts.
if you boot the phone, go into terminal emulator, type su, then type mount, and post the output, it would probably give us a clue.

laughingT said:
the external sd card has probably got your .androidsecure hidden folder on it, possibly more. if your phone had the eu bug, then CM10 recognizes that and switches the mounts.
if you boot the phone, go into terminal emulator, type su, then type mount, and post the output, it would probably give us a clue.
Click to expand...
Click to collapse
No the android secure was on the phone, The external sd card was never in my phone but I was trying different things and if i format my sd card put it in the cappy then do the flash. It will work but as soon as I turn the phone off and put the sd card in another phone, It has no files. but when I put it in my laptop it says there is only 5 gb on it but it is an 8gb memory card. Then I have to format twice to get my full memory from it on another phone.