Database Develop

Can't root no matter what I do

I have tried every forum and every article's tips on how to root and NOTHING is working. I have cupcake. I have formatted my SD card using a reader because when I try to mount it using the phone it unmounted. I installed the program onto the SD card and powered it down. I hold down the camera button and hit power. The screen with the 3 colors comes up and just stays there doing nothing. Am I just not waiting long enough for the gray screen?
PLEASE HELP!

fro0tlo0p said:
I have tried every forum and every article's tips on how to root and NOTHING is working. I have cupcake. I have formatted my SD card using a reader because when I try to mount it using the phone it unmounted. I installed the program onto the SD card and powered it down. I hold down the camera button and hit power. The screen with the 3 colors comes up and just stays there doing nothing. Am I just not waiting long enough for the gray screen?
PLEASE HELP!
Click to expand...
Click to collapse
The screen you want for flashing is the one with the exclamation mark, activated by holding down HOME + POWER, you then press alt+l to display the log or whatever. How far did you get in the process anyway, my info kinda relys on what uve given me

fro0tlo0p said:
I have tried every forum and every article's tips on how to root and NOTHING is working. I have cupcake. I have formatted my SD card using a reader because when I try to mount it using the phone it unmounted. I installed the program onto the SD card and powered it down. I hold down the camera button and hit power. The screen with the 3 colors comes up and just stays there doing nothing. Am I just not waiting long enough for the gray screen?
PLEASE HELP!
Click to expand...
Click to collapse
Oh sorry (ignore my old post) here is a good link, start from
Before We Begin on the page http://wiki.allshadow.com/index.php/G1_Root, and make sure you are on RC7 or RC9 first. You need the DREAMIMG.nbh file in the root of your memory stick

keemyb said:
Oh sorry (ignore my old post) here is a good link, start from
Before We Begin on the page http://wiki.allshadow.com/index.php/G1_Root, and make sure you are on RC7 or RC9 first. You need the DREAMIMG.nbh file in the root of your memory stick
Click to expand...
Click to collapse
Make sure your card is formatted to fat32. Make sure the file is DREAIMG.nbh and not DREAMIMG.nbh. Boot up by holding camera + power. If it doesn't boot right then redownload the DREAIMG.nbh file, could of been a bad download.

version I535 wont root or do any thin else help please. 4.4.3 kit cat yuk
I have a version Samsung galaxy S III I535 android version 4.4.3. I do not really care for Kit cat and wanted to root it like I did my girl friends. I have spent more then a month pouring over this site mostly this but others, I have tried a ton of programs with Odin, following directions to the letter. I still can not get the thing unlocked. Every program that says install with Odin fails The ones that say put it on your SD card go there but they wont install fully. hard to read fully but it says something about wrong or bad signature then more yellow letters follby more re and it quits and leave me a dead screen. So far I have gotten lucky, the only that has quite working is 4G and it does' n even show there is a router in the house so The tcpip is probably shot. Please folk Im begging for are some help my ST card runs out in two days and they are 45 dollars a piece. so hit me with the instructs, or constructive criticism. I am new to this Ive done it in a very old phone with CW on it so it was easy please from a desperate man how to get this thing to unlocked so I can rom it and put in ST card. And before anybody *****es about ST they have been great to me and mine.
Sure I went to version (worst mistake of my life except getting married,) like being married its great at the beginning then you get that first bill then it doesn't seem like a good idea for a while but after being lied to and having to pay $290.49 I gathered there crap brought it back to a version store and dumped it. The phone is mine I bought it from gur who fixes and resells phones. I have bought several phones from him both personal and to resell he does wonderful work but he is on vacation for 3 more weeks out west camping and
My phone did work great till I finger into it lol.
If some one has the time to speak English instead of android that would be even better. Please remember I am a phone retard so use small words and please oh please point me to software the will not fail while Odin is passing it to the phone, or off the sd card
Sincerely
Dan.

Sounds like you can use towelroot
http://forum.xda-developers.com/showthread.php?t=2784249
Look through this thread (page 6 and 7 seem like its been shown working)
If you have further questions ask there as they will be able to help you more than those of us watching the g1 forum
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

FINAL ADB SOLUTION: For those who couldn't get ADB with Recovery

1. Install HTC Sync 2.0.25 onto your PC (it came with your phone) (maybe the custom driver works but I haven't tried it yet)
2. Power off your device
3. Remove the battery
4. Plug in your USB cable
5. Insert your SDcard (any kind, it doesn't matter the type, i have 6 different cards and class associations in my possesion and have rooted all of my co-workers DI's today using all 6 cards for proof of concept, 9 phone total [Everyone wanted Wireless Tether)
6. Insert your battery
7. Hold Vol. Down button + Power button
8. Start and loop (you can start this before now if you wish, just has to be before entering recovery)
9. After the phone scans the sdcard choose "Recovery" and press the Power button.
*10. SOLUTION: As soon as the white screen appears just casually (don't be a speed demon) click IN & OUT your sdcard and continue to do so (keep clicking it) when the black screen with triangle appears. You will be listening for the last windows chime that identifies the USB has registered. But, you want to stop with your last sdcard click IN just before the last windows chime is sounded through your PC speakers. You might need to do this a couple times just to get familiar with the timing of the windows sounds on your computer system. Those phones that don't have to do this and was rooted first have a much earlier timing of when the Exploit is active.
11. Now go get Rooted using the steps on the first page of this post.

dymanese said:
1. Install HTC Sync 2.0.25 onto your PC (it came with your phone) (maybe the custom driver works but I haven't tried it yet)
2. Power off your device
3. Remove the battery
4. Plug in your USB cable
5. Insert your SDcard (any kind, it doesn't matter the type, i have 6 different cards and class associations in my possesion and have rooted all of my co-workers DI's today using all 6 cards for proof of concept, 9 phone total [Everyone wanted Wireless Tether)
6. Insert your battery
7. Hold Vol. Down button + Power button
8. After the phone boots up and scans the sdcard choose "Recovery" and press the Power button.
*9. SOLUTION: As soon as the white screen appears just casually (don't be a speed demon) click IN & OUT your sdcard and continue to do so (keep clicking it) when the black screen with triangle appears. You will be listening for the last windows chime that identifies the USB has registered. But, you want to stop with your last sdcard click IN just before the last windows chime is sounded through your PC speakers. You might need to do this a couple times just to get familiar with the timing of the windows sounds on your computer system. Those phones that don't have to do this and was rooted first have a much earlier timing of when the Exploit is active.
10. Now go get Rooted using the steps on the first page of this post.
Click to expand...
Click to collapse
is this while running loop.bat? it didn't say

vzw said:
is this while running loop.bat? it didn't say
Click to expand...
Click to collapse
yes run the loop.
I tried this for about an hour with no result btw.

Worked for me

Seriously , this is the EXACT same steps that has been posted numerous times before. When you speak of a Solution as something Final it SHOULD NOT involve trial and error steps that require timing or just *luck*.
What a waste of a post and thanks for im sure getting peoples hopes up.

Seriously , this is the EXACT same steps that has been posted numerous times before. When you speak of a Solution as something Final it should involve trial and error steps that require timing or just *luck*.
What a waste of a post and thanks for im sure getting peoples hopes up.
Click to expand...
Click to collapse
Yes you run the loop but not necessary to run in a loop. Yes it is about timing and similar posts have been made but I think I've written it with more detail.
These precise steps worked with the exact timing on 8 DIFFERENT phones yesterday. If its not working for you then perhaps you don't know how to follow directions well.
-------------------------------------
Sent via the XDA Tapatalk App

Ouch.... Burned by last post
dymanese said:
Yes you run the loop but not necessary to run in a loop. Yes it is about timing and similar posts have been made but I think I've written it with more detail.
These precise steps worked with the exact timing on 8 DIFFERENT phones yesterday. If its not working for you then perhaps you don't know how to follow directions well.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
You know, just because it worked for you doesn't mean it will for others....
I CAN follow directions well, and I can't get it reproduced. (though it may be because I'm already rooted?)

Just keep clicking that card in your own intervals after the white screen and you will get it. With my own proof I can contest that there is a BIG misconception that this is only achieved during the White screen. NOT TRUE!!!
Those steps are what I experimented with trying to root my own DI and it worked. I was not convinced I'd get it to work on other phones since It's been days and countless hours trying to get mine to connect to ADB in Recovery. So, one of my co-workers let me try it on his phone with his different card type, and one co-worker after the other, success! The root I did on MY phone was with an sdcard I bought that came with some of the phones (SanDisk 2gb). I didn't get a free card from VZW. I had FASTER success with this card of all 6 cards I've rooted with. It took longer with the other cards, class 4 PNY, and off-brand class 6 cards. With the 2gb SandDisk class 2 it works on the first try for every phone I've tried.
Did you have HTC Sync installed as your active driver, I really can't say if the customer driver works as I haven't tried it myself? My laptop is the latest Sony VAIO F-series with Core i7 with Windows Ultimate x64. In Device Manager, while in HBOOT my phone only showed up as Android 1.0 and as HTC Bootloader.

dreamersipaq said:
You know, just because it worked for you doesn't mean it will for others....
I CAN follow directions well, and I can't get it reproduced. (though it may be because I'm already rooted?)
Click to expand...
Click to collapse
No, and if you want to be in tune with the FINAL SOLUTION, your chakras must be aligned with Lady DI and her mysterious ways. I recommend balancing her on your head while you sleep for a fortnight, and then comes the sacrificial goat!
Seriously OP, I followed the last CARD CLICK prophet's advice and now my card mushes into lock--the DI just ain't built for the kind of abuse frenzied insert/ejection creates. I respect that you're good at what you do, but as others have found, teaching timing with http very difficult, at best.

I installed root by using an old laptop with XP... I had one point installed the HTC drivers. In this case, I had unistalled the HTC drivers and the HTC sync driver. Now I only used the SDK usb.inf drivers with the modified line for HTC incredible.

rynosaur said:
No, and if you want to be in tune with the FINAL SOLUTION, your chakras must be aligned with Lady DI and her mysterious ways. I recommend balancing her on your head while you sleep for a fortnight, and then comes the sacrificial goat!
Seriously OP, I followed the last CARD CLICK prophet's advice and now my card mushes into lock--the DI just ain't built for the kind of abuse frenzied insert/ejection creates. I respect that you're good at what you do, but as others have found, teaching timing with http very difficult, at best.
Click to expand...
Click to collapse
Oh CHAKRAS! Formula 51 reference FTW!!!! B.E.S.T. M.O.V.I.E E.V.A.R.R.R.R.!.!.!.!

dreamersipaq said:
Oh CHAKRAS! Formula 51 reference FTW!!!! B.E.S.T. M.O.V.I.E E.V.A.R.R.R.R.!.!.!.!
Click to expand...
Click to collapse
Believe it or not, I haven't seen it yet--just added it to my Netflix queue tho.
OP, can you get us a dmesg of you hitting the timing with your method? I want to see how it reacts to mounting/checking the sdcard devices more than once in recovery boot. I think good dmesg logs would help us all figure out what's going on here . . . .

From what I've seen
rynosaur said:
Believe it or not, I haven't seen it yet--just added it to my Netflix queue tho.
OP, can you get us a dmesg of you hitting the timing with your method? I want to see how it reacts to mounting/checking the sdcard devices more than once in recovery boot. I think good dmesg logs would help us all figure out what's going on here . . . .
Click to expand...
Click to collapse
It depends on how quick you insert/remove. It takes anywhere form a 1/2 second to 1 second between the initial "Slot changed from 0 -> 1" to where the card is actually mounted. If you click too fast, you never that that "mount" so you'll never get root, since it seems like the "mount" is actually causing the error we need. If you slow down your insert/remove to a slower pace, you'll get numerous mounts of the sd card. This might increase your chances of getting root because you're mounting multple times, but it makes the mounts more random then precise timing, and unfortunately, to get our error that we need, the read needs to happen at a percise time. You've seen the dmesg that was posted by 'mite.

THANK YOU OP! Worked for me :-D
My other 2 incredibles had worked consistently, but this one took your process to get.

dreamersipaq said:
You've seen the dmesg that was posted by 'mite.
Click to expand...
Click to collapse
Yeah, and I'm still wondering why he was so 'elliptical' about explaining what was going on there. I still can't figure out if it's the mount process or the mounted card that triggers the adbd event, or if a delayed sdcard process simply pushes adbd start into the recovery window, when commands such as 'adb shell' can be received by daemon for a split/few seconds. Would be nice to hear his explanation of what system events are occurring outside of what is logged in dmesg. The OP says mount event can complete in recovery/black screen, you say sdcard mount must complete before black screen, that's a big diff.
I wonder if it's possible to create a host-side script that reads dmesg, watches for card mount and triggers 'adb shell' at a much faster rate than a simple win shell 'loop'. That would be killer, and would eliminate all need for card insertion timing, IMO.

rynosaur said:
Yeah, and I'm still wondering why he was so 'elliptical' about explaining what was going on there. I still can't figure out if it's the mount process or the mounted card that triggers the adbd event, or if a delayed sdcard process simply pushes adbd start into the recovery window, when commands such as 'adb shell' can be received by daemon for a split/few seconds. Would be nice to hear his explanation of what system events are occurring outside of what is logged in dmesg. The OP says mount event can complete in recovery/black screen, you say sdcard mount must complete before black screen, that's a big diff.
I wonder if it's possible to create a host-side script that reads dmesg, watches for card mount and triggers 'adb shell' at a much faster rate than a simple win shell 'loop'. That would be killer, and would eliminate all need for card insertion timing, IMO.
Click to expand...
Click to collapse
I don't think so. Don't have the devices in front of me right now, but I believe that the phone is disconnected from the PC (that first do - do) before our window of opportunity, which means the pc is not communicating with the phone at all. So if (big if) I am correct, nothing local to the PC can be done to initiate anything AT THE TIME that we need it to.

dreamersipaq said:
I don't think so. Don't have the devices in front of me right now, but I believe that the phone is disconnected from the PC (that first do - do) before our window of opportunity, which means the pc is not communicating with the phone at all. So if (big if) I am correct, nothing local to the PC can be done to initiate anything AT THE TIME that we need it to.
Click to expand...
Click to collapse
Dat's kinda what I thought

I'll try to get you guys a dmesg as soon as possible. I'm at work right now and I'm responsible for alot of servers at a law firm in DC. (never get any free time it seems) I'm been trying to check in with you guys as often as I can. It's brutal today because we have Maintenance tonight throughout the morning.

This is what I found by myself to work for me after trying for 3 days originally.

Say what you will about the OP, but the timing is key and his post did help me out. I've tried tons of cards, every method out there and had no luck, until now. So for what's it's worth, this post was much appreciated.

HEY! Can't get adb to boot into recovery? Try this!

Follow the official method posted everywhere on this forum, I won't get into that part.
But if you've been doing all your little tricks like pushing the card in and out, or waiting for the windows chime, and it hasn't worked... stop and listen up!
Look at your phone while you're waiting for the chime. Don't do anything yet, just look at the screen. Right before windows does the sound you'll see the screen flicker. Did you see it? ok good.
When I was trying this everyone said the reconnect sound would happen before I got into the screen with the ! Triangle. Mine always happened after a couple seconds on that screen. Also, I noticed the screen always flickered when windows disconnected from the phone.
try this:
when you're trying to get your phone into recovery do the 10 minute video method, and when you see the screen flicker immediately push the sd card in. This was the only way I was, or am able to get the phone into recovery. I was able to do it successfully on 2 different incredibles this way. I used a 16gb card from the moto droid, and the 2gb PNY from wal-mart successfully on both phones.
Please don't dowse me with gas and set me ablaze! just trying to help. Never said it was a final solution, just hopefully helps someone.

Yep worked for me too, this method has been updated in the unrevoked teams rootwiki.

generic.imitation said:
Look at your phone while you're waiting for the chime. Don't do anything yet, just look at the screen. Right before windows does the sound you'll see the screen flicker. Did you see it? ok good.
Click to expand...
Click to collapse
Yep, I count from the boot vibrate and insert the card @ 7 seconds or when the scanline breaks for a second -- whichever comes first.
It's a simple rule that makes the whole process run smoothly, which is more than I could say when I started trying to root

Once again... No such luck for me. It was so much easier the first time i did it lol.

This has been the only method that has worked for me in the last week or so, and it has been very reliable. Usually get it within 5 attempts at worst. I have had success on only one pc, however, which is strange. I can move the usb to another pc after I get recovery and it works fine from there. This may just be coincidence, but it might be worth trying this method on more than one pc. YMMV.
Sent from my ADR6300 using Tapatalk

[Q] Rooting is so simple...so why am I having these problems??! PLEASE HELP!!

My wife and I have Nook Colors and I recently decided to root mine using AutoNooter. I went through all the steps, crossed referenced the steps with other sites, and went through the steps again. Here's the problem I run into; upon inserting the microSD card into the NC(while off)and plugging it into the computer using the USB cable the darn thing won't boot up.
Everything I've tried:
-a different SD card(I have now tried a 4GB PNY microSDHC and a 2G Sandisk microSD.....and a generic microSD card from my cellphone)
-I've tried loading the image from different sites and using different browsers
-I've tried different imaging software
-I've tried using BOTH mine and my wifes NC.
-I've tried it from 2 different laptops(a Toshiba and a Gateway)
-I've tried downloading the image from both laptops integrated disk reader using an adapter and I've tried loading it using an external USB card reader that reads/writes a microSD directly without needing an adapter.
-I've tried de-registering the NC and re-registering.
-I've let the NC sit for an hour while plugged in.
NOTHING. The light on the USB cable goes from amber to green....which is where the whole process ends.
-I'm running firmware v1.1.0 therefore I'm using AutoNooter 3.0
-I tried it a while back when running 1.0.1 using AutoNooter 2.12.25 with the same results. I'm getting impatient waiting for B&N's rumored update so I decided to try again.
-I do know how to format the SD card so that is not the problem
It's gotta be something simple. PLEASE HELP! Thanks for taking the time to read this. So frustrated

I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.

Sorry if you already know this but nothing happens when you boot the autonooter image. The screen stays black. All the magic just happens in the background. All the basic nooter does is enable side loading apps. Some of the others to more. Find your favorite apk and try
adb install myApp.apk
If it works then so did nooter. Find a launcher and go nuts.

vlucchetti said:
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Click to expand...
Click to collapse
Same here. I thought I botched the install but the android showed up eventually when it finally booted and I'm running market apps so i know it worked. Very weird though.

I don't think autonooter has any coding in it to prompt the screen to turn on to let you know its installing, but usually (at least in windows) when you plug in your Nook you can hear it mount to the computer...I usually wait for this, leave it on then unplug//remove the uSD card and boot up my Nook.

What are you using to "burn" the .img to the SD card? If you see the same file written to the card after burning, its not imaged properly. I had this problem the night I bought my nook and it drove me nuts. Use WinImage. From the top menu select Disk>> Restore virtual hard disk image to virtual drive>> select SD card>> select file. The burn should take about 10 secs and you should see a file system structure on the card when opened. If you get an error that the file is in use when you go to burn it, log out, log in and try again or reboot. Burning the image is key, the rest is cake.
Sent from my LogicPD Zoom2 using XDA App

chris peas said:
What are you using to "burn" the .img to the SD card? If you see the same file written to the card after burning, its not imaged properly. I had this problem the night I bought my nook and it drove me nuts. Use WinImage. From the top menu select Disk>> Restore virtual hard disk image to virtual drive>> select SD card>> select file. The burn should take about 10 secs and you should see a file system structure on the card when opened. If you get an error that the file is in use when you go to burn it, log out, log in and try again or reboot. Burning the image is key, the rest is cake.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I've used WinImage 8.5 and Win32DiskImager. I know it has to be an issue with the image but the files on the sd card after it's been written look identical to screen shots I've seen of the image on multiple "how to" websites. How long did you wait before the NC booted up?

Taeseong said:
I don't think autonooter has any coding in it to prompt the screen to turn on to let you know its installing, but usually (at least in windows) when you plug in your Nook you can hear it mount to the computer...I usually wait for this, leave it on then unplug//remove the uSD card and boot up my Nook.
Click to expand...
Click to collapse
According to NookDevs when using the latest autonooter for use with NC firmware v1.1.0 the NC will boot up automatically once it's connected to the usb cable after a few minutes. Not to be confused with the previous autonooter for use with firmware v1.0.1 where you connect, let sit for 10 minutes, then boot after removing from the usb cable and the sd card. Tried that one too with no luck.

donballz said:
Sorry if you already know this but nothing happens when you boot the autonooter image. The screen stays black. All the magic just happens in the background. All the basic nooter does is enable side loading apps. Some of the others to more. Find your favorite apk and try
adb install myApp.apk
If it works then so did nooter. Find a launcher and go nuts.
Click to expand...
Click to collapse
I never get to the point of seeing the new boot up process, skipping log-in, logging in to youtube, enabling softkeys, etc. It's funning that I quote the sequence without actually having done it. It's because I've read the steps so many times.. So frustrating!

You have to connect it to a PC to initiate the boot from SD. You should connect it to a pc where its NEVER been connected to before. A few things you can try. Connected to the PC, hold down the nook's power button for up to a minute. Did you hear a chime on the PC as if you connected a device to it? No? Next, open device manager on your PC with the nook connected. From the Action menu >> scan for new hardware. Did it find anything new? Do see anything with the name "gadget" or portable gadget in the device list? Right click, delete it. Again, scan for new hardware. Did windows find new hardware now? Did it boot from SD? Try plugging into a different PC. This is THE ctritical step.
I had this problem when i wiped my device and rerooted. Because the device drivers were already installed, my nook wouldn't boot n root. Chances are you connected it to your PC before attempting to root. You have to get windows to detect as a new device and the PC should fail to load the drivers. If you get that far with no luck, keep deleting the device from device manager and reconnecting it with the cable. Hope this helps...

vlucchetti said:
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Click to expand...
Click to collapse
Went this route and couldn't be happier with the result. Thanks so much for your input!

OP I have the same issues as you, very frustrating!
How did you solve the problem in the end?
edit: NM figured it out.

Nook not turning on

Help please
Nook color is not turning on at all. I have downloaded the clockwork recovery and burned to SD card, but it is not recognizing the power button press at all.
I have checked the mdc5 and tried the monster root pack as well as the 3.0.2.8 clockwork sd image.
I am using linux to burn the image.
[email protected]:~/Downloads$ sudo dd if=8gb_clockwork-0.7.img of=/dev/sdb1 bs=1M
7200+0 records in
7200+0 records out
7549747200 bytes (7.5 GB) copied, 578.992 s, 13.0 MB/s
Click to expand...
Click to collapse
but the power button is either defective, or not even recognized. or there is a deeper issue that I am not seeing.
when plugged into power the nook does charge, but not recognized by the laptop.
I am assuming the next step is to let the battery die, assuming that it is still on some how despite the screen being totally black and off. So 3 days maybe a week How do I tell?
If this is not the next step, suggestions?
Thanks
Mike

What were you doing when this happened and what ROM is on the nook?
Sent from my LG Optimus V using Tapatalk

Flashing nightly 201 Now thinking about it, I think that I may have formatted boot.
Mike

nrune said:
Flashing nightly 201 Now thinking about it, I think that I may have formatted boot.
Mike
Click to expand...
Click to collapse
One thing I found is that whan I can't power up my NC, use the cable to connect it to you PC and it should boot up. Then either re-flash, repair or whatever.
migrax

Yes I have tried that, no good, I think that I am going to have to wait for the battery to die and see if I can get a recovery at that point, It may take days waiting.
Mike

Is your SD card fully inserted? I had exactly the same thing happen to me over the weekend and it was because the card slipped out (permanently I am afraid) while the nightly update installation was processing.

Yes in as far as it will go.
usb charge cable turns yellow on connection, but no boot.
Will takeing it apart and disconnecting battery solve the issue or case more problems?

How long are you holding the power button, at one time I had to hold it for almost a minute before it would boot?
migrax

two minutes of hold time, no response.
Mike

http://forum.xda-developers.com/showthread.php?t=1270962
[Q] Can't unbrick my bricked NC
This will hopefully help. If your sdcard isn't burned using the correct reader you will get this exact effect.
Again, hope this helps.
Sent from my NookColor using XDA Premium App

Thank you thank you thank you!
Booted into windows, reflashed the image, connected the nook to the computer it booted, flashed nightly 201 and is now nicely charging.
thanks!!
Mike