2 Nook Colors DEAD in 2 Days
I have gone through 2 Nook Colors in 2 days now. I thought the first one was just faulty but now the same thing has happened to the second one. I'm hoping for some advice before I return and give up.
Both times I have:
Installed 2.2 to internal
Overclocked with setcpu
Installed the zeam launcher
Setup and downloaded everything as I wanted it.
Moved a few ePUB files over to SD card and ran them in the NOOK APP.
Then at some point, I turn it off and then it NEVER comes back on.
I have tried:
the power button a million times with every combination you can think of (long presses, short presses, with power cord plugged in, without, ect.)
With the first NC, I tried to install back to stock rooted with the guidance of one of the stickies. It ran Clockwork Recovery, formated what needed to be, installed the zips as it says to. Everything seems to be fine until the end when it says to reboot. It goes to a black screen and nothing new happens.
What does work:
Installing 2.2 to SD card and running just from that. The best SD card I have is a class 4 and it is sooo slow. I also just don't like this as a permanent solution (knowing that it is a brick without the special sd card).
I really like what the NC can do and I think it is a good investment but I don't think I even want a replacement. I mean, I don't want to spend another 6 hours setting one up, just for this to happen again. Please somebody tell me what I'm doing wrong and/or what I can do to fix it. I don't want to give up on this project.
Thanks in advance.
- 02-03-2011, 11:52 PM #2
- 02-04-2011, 12:01 AM #4
mine won't turn on at all - the screen is black. Though it it's plugged into usb cable and into computer, when i try to turn it on, I can hear sounds as if PC recognizes new hardware. Still nothing happens. I have 3.0 loaded on an SD card... will try to boot off that... but so far it shows no signs of life...
- 02-04-2011, 12:02 AM #5
- 02-04-2011, 02:09 AM #6
- 02-04-2011, 09:11 AM #7
- 02-04-2011, 10:10 AM #8
- 02-04-2011, 10:45 AM #9
- 5 Posts
I think I have it ... there was a post a little ways down from this one
There is a section in there about re-partitioning the boot sector and that worked for me. I had to use the zip to re-partition and then put the stock 1.0.1 rom back on.
- 02-04-2011, 10:59 AM #10
- 32 Posts
- Fission Rom|Nookie Froyo
This happened to me twice with my NC. Not sure why.. It has to do with the SD. I've been running for 4 days fine w/o an SD in.
you'll need to flash nookie froyo to an SD and restore your NC to stock and then root again. Its a pain.. not sure what my SD is doing to it but I just for now have not been using an SD
- 02-04-2011, 11:00 AM #11
Bugs, can you be more specific with those steps?
Wipe system and data. Install Froyo. Install 1.01 boot recovery. Then install Froyo again?
Also, I think you missed one point that I had in the OP. If this keeps happening and I don't understand why, and I have to keep reinstalling setting it up every so often. It isn't worth all that time and in that case I need to return it.
- 02-04-2011, 05:16 PM #14
ok seriously stop trying to flash your nook if you dont know what you are doing. its one thing to spend a few hours searching for an answer but its really annoying that you just give up and return it. thats why we have crappy return policies/ warranties with electronics
1. flash nookie froyo to nook
2. run it make sure it loads then turn it off/ install gapps
3. flash the boot recovery
4. reflash nookie froyo
it should work now. if it doesnt post your problem and i'll help you later. and for the love of god dont return it again
- 02-04-2011, 06:15 PM #15
Once you get it back up you might want to proceed in a more stepwise change and test fashion. Run it stock for a bit and make sure everything works. Then make one change and run it for a bit (like a day) before proceeding. This will provide you with some basis to determine what caused any issues.
You don't understand. I think you should reread the OP. It does not turn on. So how was I suppose to do step 1 of your instructions?
I returned the first one because it stopped working and following the restore to stock instructions in the stickie DID NOT work. I thought the device must be fried. It turns out those directions just failed to mention the boot partitioning. I was thinking of returning the second because I spent 2 days in a row at about 6 hours each day with it being wasted time. It was all gone. It is not just about getting it back up and running. I do not have the time to spend 6 hours a day to get it back up and load the things I want. So the other point that I had, that you choose to ignore, is that if I can't find the root of the problem then I still don't want this thing!
I finally did get it up and running. I'm just going to run off of a SD card instead of installing to memory and hope that stops whatever error was happening.
- 02-05-2011, 08:40 AM #17
- 02-05-2011, 04:07 PM #18
- 58 Posts
@BugsBunny, I couldn't help but to reply, I agree that those who aren't comfortable with this stuff in general shouldn't mess with internal storage stuff and definitely shouldn't return device after device.........HOWEVER, I do think that your attitude towards trying to assist the OP is somewhat snippy and unwarranted , if you don't want to help him simply do not respond, being rude helps absolutely no one, these projects get further by others adopting them and some of whom will be novices many have came here after hearing about the ease of the process and the functionality of the Nook Color from the main page news via Will Shakin. Servility will benefit us all lets not be mean and grumpy.
Hopefully someone can help "iamisac". As someone suggested take out the SD card and try booting then, or go back a few pages backMay the little green robot be with you!
- 02-05-2011, 09:12 PM #19
- 2 Posts
Glad you are keeping it.
I noticed twice in your comments that you consider returning the 2nd NC as you did the first one. I think the rooting community would agree, when you root a device you are accepting the responsibility for the functionality of the device. All of the rooting how to's start with dire warnings of the possible problems you can get into and cautions not to tackle it if you are not up to it.
In a nutshell I would be interested in the forums comments as to why this should be made Barnes & Nobles problem. If vendors get high rates of returns on devices that have been rooted we can all expect more locked boot loaders in the future.
Success: Droid, Droidx, NC,
- 02-05-2011, 11:16 PM #20
- 02-06-2011, 08:05 AM #21
- 84 Posts
Teach and Mentor
I get your frustration and I can tell you want to help. These forums are a team community. Try to temper your points with some understanding of the one who needs help. People come here to learn and try new things. You know more than others on certain subjects and are in a position to teach others. Let people look up to you and appreciate your help. I have read your posts and and appreciate you passing on your knowledge and experience. Reach back and pull others up, Bugs.
- 02-06-2011, 09:40 AM #22
That last thing people should do is go running back to B&N with some story about the device being bad. The "failed" unit will get sent in for diagnostics and we will all have issues if they start seeing a lot of units died because of screwed up rooting.
- 02-07-2011, 10:44 AM #23
i understand Bugs' frustration...it's not that the OP failed to root his NC and just quit, but that he's so quick to return it and get a new one...if everyone who failed rooting their NC immediately returned it for a new one, i'm sure B&N would step up any plans they have to prevent rooting...and that wouldn't help anyone in the community
based on the thread's title, i came to this thread thinking there may be hardware issues with the NC, but as soon as i read:
Both times I have:
i knew where it was headed...lol
Last edited by Nubio; 02-07-2011 at 10:56 AM.
- 02-07-2011, 10:54 AM #24
- 81 Posts
- Stock Moto, CM7
Agreed with everyone on here... I have several friends/co workers who have come to me about rooting devices, whether it be Nooks, or phones, etc. I make it ABUNDANTLY clear that this is not a fire-and-forget kind of thing. Rooting, adding new ROMS, etc. requires that the user keep up with updates, new methods, improvements, etc. If you're not willing to keep up with it, find a device that will do what you want stock, and deal with the manufacturer's updates. Trying to get the device to do something it's not intended for, having an issue, and then returning it to the manufacturer is NOT the way to handle this. You can't buy a car, run jet fuel through it, burn up the engine and take it back to the dealer for another one.
- 02-07-2011, 12:59 PM #25
Perhaps this post will help, I had the same issue
I went through several different methods that should have fixed it, but the only thing that worked was using dd to apply a image to specific partitions
Edit: Oddly the link doesnt seem to be working right. It's my post in the How to Restore Nook Color to rooted Stock, post #46