2 Nook Colors DEAD in 2 Days

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.


you boot from a CWR sd card....this is why people who dont know what they are doing should not be flashing their devices

i dont care anymore do what you want and if you cant find something try searching xda for it
 
You brick it, you keep it.

Mike

Agreed. Once you start rooting consider your warrenty violated and dead.

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.
 
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:
Rooted

i knew where it was headed...lol :)
 
Last edited:
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.
 
This seems like a good and useful thread. A teachable moment, I suspect. Hopefully it will have a happy ending.

The OP was probably "wrong" to have returned his first NC, and he should absolutely not entertain any thoughts of returning the second. It's pretty clear at this point that the issue, whatever it is, is only happening due to his actions.

On the other hand, it does seem like the OP has tried to do his due diligence, and has spent significant time trying to figure this thing out. I can totally empathize with him, since I'm a newbie myself.

So, the issue that the OP is hitting is likely due to a corrupted boot partition, right? Is that the consensus? The fix would be to boot off of an SD card, and start doing repairs from there, right? Is it ever the case that an NC will not boot off of anything? Is there a plan B?

Also, are "nandroid" backups useful on the NC? On my Evo, I do them all the time. The idea of having to re-do 6 hours of manual setup every time you hit a snag sounds awful to me. On my phone, I do backups before I do anything major, after anything major, at least once during the "personalization" phase, and then a few days later once my confidence in the current set-up is high. If a tragedy occurs at any point, you always have a known-good config to return to.

(Assuming of course that you can get back into recovery.) :)
 
Also, are "nandroid" backups useful on the NC? On my Evo, I do them all the time. The idea of having to re-do 6 hours of manual setup every time you hit a snag sounds awful to me. On my phone, I do backups before I do anything major, after anything major, at least once during the "personalization" phase, and then a few days later once my confidence in the current set-up is high. If a tragedy occurs at any point, you always have a known-good config to return to.

(Assuming of course that you can get back into recovery.) :)

Nandroid backups work perfectly on the NC once you have CWR installed. Restoring the nandroid backup saved my dumb ass after I inadvertently deleted the /data partition instead of the cache once. That was a nice expensive paperweight I had for awhile while praying I had a usable backup somewhere and didn't have to start from scratch setting up my Nook.
 
Nandroid backups work perfectly on the NC once you have CWR installed. Restoring the nandroid backup saved my dumb ass after I inadvertently deleted the /data partition instead of the cache once. That was a nice expensive paperweight I had for awhile while praying I had a usable backup somewhere and didn't have to start from scratch setting up my Nook.

Not sure you even really need a backup, I've seen the stock ROM available for download. Just need to have a little computer savvy to make this work.

As long as you can boot from the SD, things should work just fine.

Mike
 
Not sure you even really need a backup, I've seen the stock ROM available for download. Just need to have a little computer savvy to make this work.

As long as you can boot from the SD, things should work just fine.

Mike

You're right that a nandroid backup isn't fully needed since you can flash the stock ROM, but I hate going to the trouble of restoring all my apps and settings. A nandroid snapshot is good for the lazy like me. :)
 

Trending Posts

Forum statistics

Threads
957,274
Messages
6,972,177
Members
3,163,751
Latest member
CassiveMock