Database Develop

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.

For developers. Root Info. Hope this helps

Hey,
I have been trying to root since the minute the process was let out publicly with no luck, until this morning. I have been through each thread over and over and finally found several things that made it work. After completing the task and going back over everything I tried. I found out the following and I would bet good money it will work for any one.
1. I left my phone plugged in the whole time. No usb cord inserting
2. I had it set to disk mode under pc connection in settings.
3. I used the 2gb card from verizon. Did not erase it. Don't know how it was formatted and don't believe it matters.
4. Made sure the HTC driver was working. This was done by having phone plugged in while in normal operating mode. To verify this once you hear the usb sounds in the command window at the C:/whatever/tools prompt type adb devices. It should come up with a serial number or such.
5. This will sound odd, but several of the methods talk about the screen flicker and not many talk about a sound the phone makes when it loads the sd card. That sound is real and audible if you put the phone to your ear. try it when you turn your phone on. You can hear it. That sound is the key. Try it by starting your phone normally and put it up to your ear. You will hear it.
6. Ok, if your phone is recognized by adb and you can hear the sound you have all you need. Make sure you have the necessay files downloaded to your tools folder.
7. With your phone in normal operating mode, shut it down. You need access to your battery and your sd card so the back needs to be off.
8. Pull the battery and unclick your sd card, hold Vol- and power. The phone will start and try to load the bootloader and leave you at the screen where you can select recovery.
9. Start Loop.bat
10. Press Vol - to select recovery and press power. move the phone close to your ear with your thumbnail on the sd card. When you hear that sound, immediately click in your sd card. The phone will goto the black triangle screen. The phone will then go through it's usb detection and when you hear the connected sound, you will get the error message. This may take 15-30 seconds. It took me 2 tries the first time, but now I have gotten it everytime I have tried since.
11. type in adb devices to verify that your in recovery.
12. Use your favorite method from here. The xda method is the one I used. Everything works fine. Wireless directly to my IPAD.
I think if I made a spread sheet of all the methods, sd cards and timings, we would find out that this is usually the thing that works. You can use the clock method, but I guarantee the right time collates with the cricket sound which collates with the screen flicker.
Anyone else smart that cares to look at this may be able to figure a way to streamline it even more.
Rod

sorry buddy but this old news we all knew about the audible sound, most people tried clicking in the sd card at that point, others tried plugging in usb at that point, buts we all knew about the sound and tried different methods to get it to work. personally i tried your method and it didnt work before i actually rooted. the method i used, envolved a linux live usb flash drive, linux live sd card formatted, and the tail messages, worked everytime the first time, if i missed the first time i had to restart the entire process. atleast now you are rooted

Jesus, everyone has a method that works for "everyone".
Apparently "Search" is broken?

aaronjb said:
Jesus, everyone has a method that works for "everyone".
Click to expand...
Click to collapse
I hear what you're saying, but we shouldn't stifle discussion that could lead to a more reproducible method, either. Maybe this doesn't warrant a new thread, but whatever.
Anyway, I had tried several of the other methods before, maybe 20-30 times, but nothing worked. I tried to time it with the click sound a couple times before, and it didn't work, but I thought I'd give it another try, since OP mentioned he got it to work with the stock 2GB SanDisk card, and that's all I have.
This time, I got it on the second attempt. My reflexes were a little slow, so it was probably more like a half-second after the click sound that I managed to click in the SD card. I haven't attempted to get back yet, so I don't know how repeatable it is.
One thing that may or may not be worth trying for others is that right before I got it, I uninstalled HTC sync, installed the bootloader drivers from the unrevoked site (can't post URL since I'm a noob).
Then uninstalled them (check "delete drivers" when doing so they won't auto-reinstall), reinstalled HTC sync, and finally reinstalled the bootloader drivers. I did the last reinstall because the device wasn't showing up when the phone was in the bootloader menu w/just HTC sync. It's unclear if any of this made a difference, or if I just got lucky with my timing this time.
When I was booting into recovery and pushed in the SD card, very shortly afterwards, I got a balloon in the bottom right that said it was installing the drivers (again? is that expected?). After that, rewt!

Oh lord, if I never saw another one if these threads, I could die a happy man. They're about as useful as alchemy, phrenology, perpetual motion machines, astrology, cold fusion, x-ray specs, etc etc ...
Sent from my Hal90000 using XDA App

The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.

adrynalyne said:
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
Click to expand...
Click to collapse
Because the title is so vague that you don't know it's YARMTISWWFE (Yet Another Root Method That I'm Sure Will Work For Everybody) thread until you read it?

If you couldn't figure out the post content by this time:
I have been trying to root since
Click to expand...
Click to collapse
Then some folks here might want to get tested for some learning disabilities. Don't even have to finish the first sentence to figure out what this thread was about.

To become rooted, do you have wipe your phone and sd card?

No, you definitely do not need to do that.

adrynalyne said:
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
Click to expand...
Click to collapse
I wanted to see who was pretentious enough to think that their hare-brained scheme for rooting needed a new post, why they thought their experience could possible impact developing for the Inc, or what could possibly justify tacking "for devs" on the title of their post--as if they succeeded in making a secret club of a thread by doing so.
If he/she really wanted to help devs, they might have PM'd the guys involved with Unrevoked first, or joined their IRC channel, rather than clogging up the forum with another rooting thread. Honestly, there's enough going on now to think of others' purposes here before your "eureka" moment. Too bad I had to bump this thread just to respond.

Why be so mean? The more discussion on obtaining root the better I would think. Maybe this topic was not helpful but another one someday might and if people like the rude folks bashing the OP in this thread make others afraid to post then we might never get a reproducible method.
The sooner we get a reproducible method the better, because that means more folks to test and a wider user base for ROMs. I dont think a developer would spend too much time on a ROM for a device that they do not own and feel only a handful of people would have access to.

Oozura said:
Why be so mean? The more discussion on obtaining root the better I would think. Maybe this topic was not helpful but another one someday might and if people like the rude folks bashing the OP in this thread make others afraid to post then we might never get a reproducible method.
Click to expand...
Click to collapse
You call it mean, I call it strongly discouraging more speculation on a topic that already has a dozen or more threads going. As you can see by the proliferation of more advanced thread recently, most have moved on from trying to root, which common sense would tell one is caused by most having figured it out.

Maybe everyone has figured it out, maybe not. I imagine if you started a thread and asked who was still trying you would get several folks respond that they were. Nothing indicative of the entire population but just saying.
Edit: I just saw your avatar and then your use of such excellent gramar and vocabulary above. Did you make your own lingwo(sp) robot?

This thread has turned into a flame fest against the OP (since pretty much the beginning of it). Thread closed.

Afraid I have a $250 paperweight..root issue

As I have posted in a development thread about rooting..
Alright guys, I have a problem. And there is very little info about doing this on a Mac
I have created the autonooter2 sd card using terminal.
My nookcolor is powered off, sd card inserted, nook USB cable plugged in to nook and then computer. (nook symbol lights up on cord), my mac pops up and shows a RNDIS ethernet device
-1 st problem, It says on nookdevs that this RNDIS dialog will pop up and to ignore it...does that mean ignore it, leave it there or click cancel? I have tried ignoring for a while and then clicking cancel.
- It says both here on xda and there that when the autonooter is finished the nook should reboot itself..its been 10 mins this never happens??
any help is appreciated
edit:
alright I just unplugged the USB and turned on my nook and it brought me to the Android setup screen. I skipped the tutorial and sign in and checked both location boxes and then when I clicked continue the screen flashed and it threw me into the normal B&N interface and the nook color user guide automatically popped open and starts flipping pages rapidly. I can close out of the user guide but then it auto reopens :/
edit2: restarted , everything appears to be working alright except I cannot pull up a keyboard in any instance...searching store or through books
edit3: i have tried erasing and un registering my device. my nook is now unregistered. I have been trying to get rid of root. i have cleared data ( power+ volume + nook button) but I cannot factory reset using 8 reboot method.
My device is on, has NookColor settings under extras but I have no keyboard and cannot connect to wifi or re register..
Please.... help

You should register your NC prior to rooting it. You can restore your nook to its fresh state by interrupting the reboot process 8 times or, using the Android Debug Bridge (instructions for enabling it here: nookdevs.com/NookColor_USB_ADB) by following these instructions: nookdevs.com/Flash_back_to_clean_stock_ROM. Once you're done with that, register your Nook and then follow the AutoNooter instructions (nookdevs.com/NookColor_Rooting). Note: autonooter will reboot by itself once it's done; don't interrupt it by restarting the nook by yourself!

Ok quick question..
I figured I could not do any more harm so I started the autonooter process over from start to finish remaking the sd card but this time on a PC.
Everything worked better, the nook auto restarted itself and I got the Nook Color Dev screen and then to the unlock screen. I unlocked, ready to do the next steps (skipping tutorial and skipping gmail sign in) but I was never prompted. I am just at the normal nook homescreen, I now have much more options in extra( superuser, email, etc) and also the soft keys but I still do not have a keyboard.
Since I did this autonootering from an unregistered device do I need to start completely over?
Thank you for your response

foethalove said:
Ok quick question..
I figured I could not do any more harm so I started the autonooter process over from start to finish remaking the sd card but this time on a PC.
Everything worked better, the nook auto restarted itself and I got the Nook Color Dev screen and then to the unlock screen. I unlocked, ready to do the next steps (skipping tutorial and skipping gmail sign in) but I was never prompted. I am just at the normal nook homescreen, I now have much more options in extra( superuser, email, etc) and also the soft keys but I still do not have a keyboard.
Since I did this autonootering from an unregistered device do I need to start completely over?
Thank you for your response
Click to expand...
Click to collapse
It doesn't sound like you have anything resembling a paperweight, I'm sure you'll get it to where you want it.
Did you try the steps of signing in youtube then gmail, then market? If your only problem is a missing keyboard, that can easily be remedied. Get the apk of a keyboard that's known to be working (there's a thread in the NC section on the DroidX kb), and push it via adb as system/app/LatinIME.apk. Reboot, and you should have a keyboard.
You said you can't do the 8 failed boot attempts... Why not? All you have to do is power-down 8 times during boot (hold down power for about 10 seconds, then hold down again to power on... Repeat 8x).

Hey,
I'm kind of in the same position that you were originally in. My NC's firmware is 1.0.0. I used the guide on nookdevs.com, flashed my SD card w/ the proper image, inserted the card, plugged in the USB, and... over 30 mins and nothing.
What did you do once you were in this step to continue? Did you remove the SD card?
-Taser
edit:
wvcachi, that's actually exactly what I ended up doing, and it came right up - thank you!
Also, I ended up doing this (sorry, no linking allowed - nookdevs.com/Installing_the_1.0.1_update_on_a_rooted_NC), re-rooted, and the 1.0.1 root actualy did auto-reboot.
Thanks eveyone for your help, and OP for not getting too ticked I hijacked their thread

Taser420 said:
Hey,
I'm kind of in the same position that you were originally in. My NC's firmware is 1.0.0. I used the guide on nookdevs.com, flashed my SD card w/ the proper image, inserted the card, plugged in the USB, and... over 30 mins and nothing.
What did you do once you were in this step to continue? Did you remove the SD card?
-Taser
Click to expand...
Click to collapse
Ya same issue here, except now my nook is stuck at the giant n. It was responding to my adb shell commands to to the 8x reboot for the BootCnt. But after it did the update it still sits on the giant n. I'm not sure what is screwed up on mine. I wonder if the auto-nooter just messed up some how...
I was upgrading from 1.0.0 to 1.0.1 to fix my wifi drop issues.
Edit: Just let the n sit there for a good 15 minutes. I've never been so happy to see that intro video with that girl showing you how to use the nook!
Will try to auto noot again...

I've done auto-noot several times now, and it's never rebooted on its own. After a couple minutes of it doing its thing, I just unplugged it, held down power for 10 seconds to power off (it's on even though it doesn't look like it), removed the SD, then powered on. Everything was as expected after that, it just never rebooted on its own.

Mine from 1.0.1 behaves exactly like the wiki described for me. Ran with the screen off for about 45s and then rebooted and was good to go. I followed the post instructions to set up the account and everything went exactly as they described. Only difference was it seemed to me like the instructions duplicated themselves at one point, steps in had already done were listed.
Works great, but might should revise the steps of there are duplicate ones. If I remember or root again I might do it. Adding renaming the phone apps woukdvbe a good thing to do too.

The version of Auto-nooter for 1.0.0 doesn't auto-reboot after it's done. You'll have to let it sit and reboot yourself.

I strongly recommend you upgrade to 1.0.1 before you root anyway. It's more stable, and when you eventually upgrade, you'll have to wipe your nook to do it. Better to do it while you don't have anything on it.

Thanks to everyone that helped out. I have everything up and working!

Power button won't turn on NC

I'm rooted with latest Auto-nooter as of last night. The power button on the side works fine with turning off the screen and turning it back on and with turning the device off with a long hold. However, once its off, the switch won't turn the NC back on and I have to plug in the usb cord in order to turn it on and it takes a while. Anyone have this problem and find a solution?
This is my 2nd NC and the first one didn't do this, although I might be returning this one too because the bezel is a little loose in one corner.

Read this...
http://forum.xda-developers.com/showthread.php?t=871996

epakrat75 said:
Read this...
http://forum.xda-developers.com/showthread.php?t=871996
Click to expand...
Click to collapse
Sorry please move this to the General forum

I had the same problem with my first run of autonooter. I already had youtube, su, etc when I tried autonooter, which may have been the issue.
To resolve it, follow the instructions to completely wipe nook (system and data areas). Install 1.0.1 update. Then run autonooter again. Be sure to pull the usb cord when nook reboots after autonooter has done its magic. Doing this fixed mine. Good luck!
Sent from my LogicPD Zoom2 using XDA App

Remove the autonooter card. replace it with a fresh card so that you can actually use it.
Sent from my rooted droid x

Syco54645 said:
Remove the autonooter card. replace it with a fresh card so that you can actually use it.
Sent from my rooted droid x
Click to expand...
Click to collapse
thanks I just formatted it right within the NC and now it boots up with the power button, lol. Thanks.

tomtbone said:
thanks I just formatted it right within the NC and now it boots up with the power button, lol. Thanks.
Click to expand...
Click to collapse
Are you the same tomtbone from VS?
I did it all from my Nookie...

cal3thousand said:
Are you the same tomtbone from VS?
I did it all from my Nookie...
Click to expand...
Click to collapse
why yes I am lol. moving on to Swedespeed with my S60R though. THe 855R is sitting in the driveway collecting dust.

NEWBIE...HELP!! Did I brick the NC??

HI All,
So, i have a brand new NC. I was eagerly looking forward to using it as a tablet.
So, here are the steps:
1. I open it, turn it on, register it on B&N, play around with it; power it all the way down. (never hooked it up to my PC).
2. I burn auto-nooter3.0 on to a microSD card (using http://forum.xda-developers.com/showthread.php?t=942424) as my gospel.
3. Place microSD card in NC; hook up to PC -- and, nothing.
It does absolutely nothing. it doesnt boot up, it doesnt do anyhing.
now I can't get it to turn on at all.
Thanks for your thoughts on what I should do next??

Have you taken the SD card out and tried powering it on?

I'm not sure exactly what went wrong, but I would re-read the auto nooter steps, and like said above remove your sd card and see what happens.
Also you need to read more of the forums and see the NC is extremely hard to brick...
and figure out the multiple ways to fix it. there are forums where you can post issues with the bricks and i'm not sure the dev forums is where you want to do that. Many devs may not have time to help you and those who are skilled in this area aren't searching here.

Sometimes it takes hitting the power button several times in a row before it responds.

Yes, took out the microSD card, and tried to power on--- and, nothing. it

Take your power cord and plug it in and press the power button repeatedly somewhat fast until you see the screen flicker, then stop.

I see you missed the first step. Charge it up. Try plugging it in for a while

Hold the power button down for 5-7 seconds until it resets
Sent from my NookColor using Tapatalk

When you plug the nook color into the computer IT WONT DO ANYTHING!!! WAIT FOR IT. Turn the sound up on your computer you'll hear it connecting, disconnecting, etc. Just be patient, jeez! Learn to carefully read.
Sent from my NookColor using Tapatalk

Autonooter 3.xxx.x is for B & N firmware 1.1 You said your NC was brand new... out of the box it could have 1.0.0 or 1.0.1 firmware as well--most likely it wasn't 1.1 If you turn it on and off enough times (theres a correct point at which to turn it off as it is still booting, then turn back on--repeat 8 times) it will trigger a self-repair back to stock. You can get the side-load update and instructions from 1.0.1 to 1.1 from B & N web site. Your NC is not a brick, it's just feeling lousy at the moment

You still broke?

I feel your pain
Try viewing these videos and following the directions EXACTLY. First go back to stock, re-register your NC with B&N, make sure your firmware is updated to 1.1.0 (this is important because autonooter 3.0 can only be used with that firmware), get a gmail account if you don't have one, then try to root again.
To go back to stock:
http://www.youtube.com/watch?v=U_gNvZGSJD4
Rooting with autonooter:
http://www.youtube.com/watch?v=MUoHALWvPts
Written directions here:
http://forum.xda-developers.com/showthread.php?t=942424
Good luck!