Related
A couple weeks ago I bought a Nook Color on ebay. The first thing I did was turn it on and let it fully charge overnight. I noticed that it was in normal condition, but didn't bother going past the intro screen since an off the shelf Nook Color was not what I was interested in anyway.
The next day I flashed phiremod 6.2 on it with no problems (I have done this process successfully to two other Nook Color's by the way). I am able to connect to my wifi, setup my google account, and open the market. Life is good so far. Then I notice in ROM Manager that there is a phiremod 6.3 version out. I try to download phiremod 6.3 from ROM Manager for an entire day with no luck. The download just kept stalling on me. No problem I'll just download phiremod 6.3 onto my sdcard and flash it through clockwork recovery as normal (performing a full wipe first of course).
Then boot loop for no reason I can tell. Just a boot loop at "Touch the future of reading" with no way to get into recovery without restarting it with the sdcard.
So I put the sdcard back in and wipe and reflash phiremod 6.3 with the same results. Then I wipe and reflash phiremod 6.2...boot loop again. I repeat this process until my eyes start to bleed.
At this point I'm thinking, "There's no reason this should be happening. I wish I could just go back in time and start over." That's when I find this link: http://forum.xda-developers.com/showthread.php?t=914690
Ok, I'll just restore everything back to stock. No clockwork, no phiremod, just Barnes and Noble software just like the day it was born. So I go down the road of restoring the device to stock and instead of bootlooping at "Touch the future of Reading" it bootloops at the "N" screen. I'm running out of ideas so I perform the 8x method, get the OTA install, and still bootlooping at the "N" screen. Oh yeah, and "power + n" wont take it into recovery of any kind.
Now that it seems that I've failed to restore the device to stock, I try to flash phiremod 6.3 again because this is really my end goal anyway. This time it is a success. I connect to my wifi. The device says I am connected and the wifi signal is strong, but I can't establish a reliable data connection with google, or open the market, or browse the web. I turn the wifi off and on, I tell it to forget my connection and add it again, but nothing seems to work until a day later when it suddenly establishes a connection.
So everything seemed like it might be ok at this point except strange things started happening with the device. Power + n doesn't take it into recovery, and never did at any time it has been in my possession. When I try to go into recovery from ROM Manager after flashing CWR I go into a bootloop. This is even after updating Rom Manager and doing things like rebooting after flashing CWR. Wifi always says it's strong and connected but any app with internet access is often times painfully slow to the point of being unusable or at least impractical. Downloading a single app from the market is like pulling teeth, and I regularly get the "retry or cancel" popup over and over again. Sometimes when I tell it to reboot or shut off, I get the "rebooting" or "shutting off" message and it just grinds away endlessly.
The device is currently in a bootloop after just telling it to reboot (normal reboot not reboot into recovery), and I know how to pop in my sdcard with CWR and get out of it. However, my problem is that this is a gift for my sister, and I just cant seem to get this device into a normal working state that I can give to her.
I know that there are plenty of threads answering all of the little problems I have outlined here, but none have resolved them for me nor have I found a single thread that deals with a whole host of problems like this device seems to have.
Thank you for your patience in reading this.
Try restoring to stock 1.2:
http://forum.xda-developers.com/showthread.php?t=1050520
It can't hurt at this point, and it may get you fixed.
Thanks for the reply.
No dice. I tried both of those files. I made sure to format the system and data before flashing each time, and I'm still stuck at the "n" screen.
Alright so here's what I just did:
1) Format system
2) Format data
3) Flash B&N v1.1 "old" 1GB "/data", 5+GB "/media" partitioning zip from:
http://forum.xda-developers.com/showthread.php?t=1094371
4) Reboot
5) Flash Stock 1.2 update.zip from:
http://forum.xda-developers.com/showthread.php?t=1050520
6) Unmount sdcard
7) Reboot
8)Still stuck at the "n" screen.
The story so far:
I was forgetting to do the 8 reboots after repartitioning and flashing stock apparently.
I performed the 8 reboots, and my Nook did a factory reset and OTA update. Now it boots into stock v1.1.0. I see the pretty lady, there's a video, I get to accept a B&N agreement, I connect to either of my wireless connections, but after I enter my account name and password it always says "Error sorry we're having trouble setting up your Nookcolor. Please shutdown the device and try again...." It gives me a number to call so I do. After a long bewildering conversation with tech support, I'm told that my device was once registered to someone else (which I already suspected having purchased it on ebay). I'm told that in order to fix the problem they are going remove the old account from the device, and that when I restart it in an hour I will be one with the Nookcolor universe. It has been many hours, and I am still getting same error message.
Should I continue down this path with customer service (who are failing to inspire me), take it into the Barnes and Noble store this weekend (I don't have a receipt but it at least it boots into stock now), or just go ahead and load phiremod 6.3 (which is my end goal, but I want to make sure I don't take one step forward and then two steps back now that I've gotten this far)?
"Device Info" only has "back," "power off," and "reset."
I just tried holding the "power + n" for 10 seconds as demonstrated here Nook blocked after downloading latest software - Barnes & Noble Book Clubs. This guys seems very happy that this solution worked for him. I don't know why it wont work for me seeing as I have the exact same problem.
Barnes and Noble tech support came through and reset my device. It appears that I have a stock 1.1 Nook Color and all is well. I am even connected and able to browse the internet. Does this mean I am ready to start flashing new ROMs onto it, or should I do more testing while it is still stock?
So I made a nandroid backup of the stock system with no problem. Then I flashed phiremod v7 test. Everything was going well until I went to ROM manager, flashed CWR, and tried to make a backup. It went into a bootloop so I put in my sdcard with CWR. Immediately it started putting my backup on that card. I rebooted it through CWR, but it still went into a bootloop. I then did a factory reset, full wipe, and flashed phiremod 6.3... still bootlooping away. This is one of the problems I was having before I started this thread. The CWR on my sdcard is ClockworkMod Recovery v3.0.0.6.
Sorry to read that you're having so much trouble. FWIW I'm having one hell of a time using Phiremod on my NC, too. I've found solace with CM7 nightlies and the latest Dalingrin kernel.
CWR 3.0.0.6 is very outdated at this point. I use CWR 3.2.0.8 on my recovery SD. I think it was V3.0.0.6 that had problems formatting the data partition, but I could be wrong.
Hope you get it sorted out.
Thanks for the support. Do you know where I could find the latest versions of Clockwork?
There's a typo in my post above. The current version is 3.2.0.1
I read about it and got the files from androidforums.com, although I'd be surprised if they weren't on this forum, too.
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR, and now it is endlessly scrolling through the CWR menu on its own. The log at the bottom says "ClockworkMod Recovery v3.2.0.0," then "Back menu button enabled," then "Back menu button disabled," then "Back menu button enabled," and seems to be continuing like that without end. After powering off, removing the sdcard, and holding the power + n buttons for about 8 seconds, the screen shows the cyanogenmod logo and says "booting into recovery" but does nothing. I've repeated this entire process several times while holding the power + n buttons for varying times and it still doesn't actually boot into recovery.
Wulfie6 said:
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR
Click to expand...
Click to collapse
This is the problem. The nook color is the encore not the bravo. You have the wrong recovery image. Its a good thing its unusable...you might fubar your device if you were actually able to use that recovery.
Sent from my Phiremod Nook Color using XDA Premium App
I created a new boot disk with CWR 3.02.8 and successfully flashed Phiremod 6.3 and CM7 nightly 107. I was still essentially unable to use the internet on both of these ROMs even though my wifi connection said it was good. I did not try using my phone as a hotspot with these versions.
I'm on CM7 108 at the moment. I'm still getting sporadic internet access even though my wi-fi is pretty good (usually just shy of full bars). I connected to my phones wi-fi hotspot which produces full bars on the Nook with good internet results. This isn't practical though because I can't always have my phone creating a wi-fi hotspot. Doesn't this seem odd that my Nook is only internet reliable when it's connected to an excellent wifi connection, but functionally wont work when it's on a good wifi connection?
Also when I go into ROM Manager and try to flash the current version of CWR, it pulls up the "confirm phone model" (when it is actually connecting to the internet) but as soon I put my finger on the menu to scroll through, it selects the first one I touch. This is one of the problems I was having before on all ROMs.
So I just went into ROM Manager, flashed the latest version, then tried to make a backup through ROM Manager, and now I'm in a boot loop again except this is the kind of bootloop where I can't get it to turn off. It just sits there with the cyanogenmod logo saying "Loading..." When I hold the power down, it turns off and then comes right back on. When I hold power + n, it does the same thing but instead of saying "Loading..." it says "Booting into recovery..." I don't understand why this time it's different. If I take out the card that's in there now and put in my bootable SD card while it's in the boot loop, will it fry my cards?
Wulfie6 said:
S When I hold the power down, it turns off and then comes right back on.
Click to expand...
Click to collapse
sounds like it's plugged in
TheAmazingDave said:
sounds like it's plugged in
Click to expand...
Click to collapse
It's not plugged in.
Return to stock 1.2 - Stuck at n screen fix.
After you flash the 1.2 image with a clockwork recovery sd boot card, and are stuck at the n screen, you will need to restart and have the Nook software reset to default.
1. Hold Power+n for 8 seconds, release n, then power (it may take a couple of tries to get it right).
2. At the "Factory Reset" screen, confirm your intention to reset to defaults (press "home" n).
3. At the "Are you sure?" screen, confirm again (press "home" n).
It will then go to a "Clearing data..." screen and reboot to the stock nook software.
This procedure will reset your device to stock 1.2, just as it was when it shipped.
I second what JoeInternet says. You NEED to be on stock B&N 1.2 to be able to run the latest CM7 builds and ANY .32 Dalingrin kernels or it will not work.
Quick thought... The first thing that should have been done is an ATO 'deregister' to get that nook's ID dis-associated with the original BN account.
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
The Device:
Nookcolor Refurb - came with stock 1.2 installed. Rooted with CM7 - initially had boot partition problems and went back and did the fix for it. (was using an old CWR, so had to redo that, too). Worked mostly fine for a few weeks. Had a little trouble installing the recent cm7 stable update. But after clearing and redo, no problems. Then I updated Adobe flash to 10.3 through the market. bad, bad, bad. (I've discovered). It has gone into a bootloop, but it doesn't even get in far enough to bring up CWR either internally or on a bootable SD card. It brings up "loading" - whether in CM7 or CWR - then shuts itself off. I have tried the 3 button salute and 8 interrupted boots, but neither works in any way. Is there something else I can do?
Also, a side note, the device will not charge to green light - even if charging overnight. At first I thought it was a battery issue, but after a day of combing the boards, I'm thinking bootloop from hell.
Help!!!!
Are you running CM 7 internally or from a card? If internally, try making a bootable CM 7 card and booting from that.
I am running it internally. The device will not boot from a card or internally. It doesn't get far enough into the boot before it loops for CWR to start up - either internally or off the sd card. I can get to the boot menu (hold down n when it starts up), but it doesn't boot off any of the options there, just goes to black screen.
What happens when you do the 8 failed boots?
Nothing really happens with 8 failed boots. I think it terminates the boot process before it gets far enough along for it to "count". Loading comes up, I count one thousand one....all the way to one thousand seven. Then it shuts off, often reboots itself. Same deal with CWR. Loading comes up, count to 7, shuts off. I can get to the boot menu in CM7, but I it doesn't respond when I request any type of boot from anywhere. Either hangs or restarts.
I'm trying ADB, but it won't stay connected. Flicks on right at the end of the loading process and then shuts down. It really sucks.
Shelly, shoot me a pm... i'll give ya my phone number and we'll work on getting it going.
Sorry if this is redundant, but in very basic troubleshooting have you tried charging your Nook? It probably is more complicated/serious than a low battery, but it wouldn't hurt to rule it out.
I finally did get it to charge to green light. Didn't make a difference. I can get it to hang sometimes when it's trying to get into CWR. And it will stay on the Boot Menu.
Just a side note, I have another NC that I've had since Jan. Autonootered, Manual Nootered, CM7ed, brought back from the dead many a times.
Dizzy Den - am shooting you a message shortly. Thanks.
Has this been solved? If yes how?
Could you find a solution to your problem?
I'm having the same issue now. Bought a Nook Color in November, Autonooted, flashed recovery from ROM Manager, flashed CM 7.1.0 internally from downloaded ZIP files via ROM Manager, was working just fine for a week, stable, fast, perfect. Overclocked to 1200 MHz after a few days which made the experience even nicer.
Then installed and started Google Maps which didn't work - the Nook turned off on launch of Google Maps app.
I had set Wifi to "stay on all the time" beforehand (which might have been bad because it creates Sleep of Death syndrome as i now know).
Now when i turn it on it shows "Loading" for 7 seconds and then the screen turns off. This is when booting CM, when booting the internal recovery (shows "loading recovery" for 7 seconds) and when booting from any SD card image (i've tried at least 10 different bootable SD card images, different cards and different card readers).
It recognizes and tries to boot off SD cards - i get different "Loading" screens depending on the image, honey-colored for a honeycomb image, with two skulls for a recovery, ... So that works.
The nook seems to be in some kind of "on" state because i need to hold the power button to turn it off before i can get it to boot again.
I can get to the boot menu as you could, but booting from there doesn't do anything at all. So the hardware seems to be OK because the boot menu itself works well and for more than 7 seconds.
I can charge it and it goes to a green light so it's no battery issue.
The nook does not show up on USB - well once it did for a second but that was it.
I even tried to let the battery run completely empty so internal registers can get reset - didn't change anything.
Help! Is it bricked now?
Going to a B&N store isn't an option btw - the next one is 6500 km from here.
(This is the first time i ever ask for help on a forum. I am running a ZTE Blade with CM7 just fine, and I've been stuck often enough but always found a solution myself...)
Gunnar
Have you guys tried this:
http://forum.xda-developers.com/showthread.php?t=1308304
Or completely restoring it to stock:
http://mrm3.net/nook-color-recover-any-bricked-device/
Tried, can't get far enough
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
tralulu said:
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
Click to expand...
Click to collapse
When you overclocked it, did you notice it getting hotter than usual? I wonder if it was due to the overclocking. All the users I see with unrecoverable nooks is after they overclocked.
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
tralulu said:
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
Click to expand...
Click to collapse
I own 4 of them so I would prefer the term "Unbrickable", but at this point I'm not really sure.
Try 8 failed boots and see if you can get into recovery to reset to factory.
cant get it working
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
tntviper1 said:
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
Click to expand...
Click to collapse
how did you write the image to the SD card? you can't just do the write button in winimage, you have to use the "convert virtual hard disk image to drive" or something... really should be mentioned in the n00b guides.
Sequence in winimage:
Disk->Use disk (whatever your sd card is)
Disk->Restore virtual hard disk image on physical drive (select the image you're trying to write)
Click ok on the warning and you should have a boot disk
"Write disk" is prominent but just copies the files to the disk, not resize or make it bootable.
Nope - no change
DizzyDen, nope, 8 failed boots does nothing. Just fails 8 times, no restore.
I flashed the nook tablet firmware on my nook color, after a stressful day at work and not realizing what forum I was downloading roms from. All i get is a black screen, I have tried flashing recovery images with no success. Has anyone else done this and recovered?
Have you tried this?
http://forum.xda-developers.com/showpost.php?p=25405429&postcount=13
Yea. I don't get any power at all to the screen. I have tried to flash cm7 recovery roms also with no success.
enjoyed said:
Yea. I don't get any power at all to the screen. I have tried to flash cm7 recovery roms also with no success.
Click to expand...
Click to collapse
Tried using a CWM Bootable SD? Link
And also repartitioning the Nook by following this.
You might want to try holding the power button for a full 15 seconds... release it... and hold it again for a few seconds and see if it turns on then.
enjoyed said:
I flashed the nook tablet firmware on my nook color, after a stressful day at work and not realizing what forum I was downloading roms from. All i get is a black screen, I have tried flashing recovery images with no success. Has anyone else done this and recovered?
Click to expand...
Click to collapse
That is not supposed to be possible. There are assert checking codes in the zips to prevent that. How did you do it? Are you sure you have a nook color? The nook color has a black bezel and the nook tablet has a silver one.
Edit: I just looked at the CM9 alpha for the Tablet. It does not have an assert check in it. So I guess it is possible.
I recommend going to my tips thread linked in my signature and making the 5.5.0.4 CWM card. I would boot to that and wipe /system. That is where most of the files get put by the Tablet CM9 zip. The problem is going to be /boot. Some of the Tablet boot files are named the same as nook color, but are entirely different. (mlo, u-boot.bin). You need to get rid of those. Ordinarily flashing a new rom will replace those, but not sure they will now. You have two choices. Use adb to access /boot and remove the files. That takes a little expertise. Or you could use an older CWM (3.2.0.1 or older) card to wipe /boot (that option was removed in the new version, with good reason.) Ordinarily I tell people to never wipe boot because it wipes the CWM stored there too. But in your case you need to get rid of those tablet files.
EDIT 2: I just did some more research and all of the Tablet ROMs I could find did have assert checks in them. That one I referenced above was one I manually modified to install on a bootable SD. So I am having difficulty figuring out how you flashed a tablet ROM to your color. Since you have not responded to this post, I assume you figured it out, gave up, or were wrong.
Sent from my Nook Color running ICS and Tapatalk
I just flashed the newest build to my Nook Color and now the device will not turn on at all. I tried holding down 'power', 'n', as well as 'power', 'n', and 'volume +' and nothing happens. There is no flash on the screen - it is just blank. The device is fully charged, it just won't turn on. I have tried several times (and over several days) to try and turn it on, but to no avail. Any advice?
boomerjr622 said:
I just flashed the newest build to my Nook Color and now the device will not turn on at all. I tried holding down 'power', 'n', as well as 'power', 'n', and 'volume +' and nothing happens. There is no flash on the screen - it is just blank. The device is fully charged, it just won't turn on. I have tried several times (and over several days) to try and turn it on, but to no avail. Any advice?
Click to expand...
Click to collapse
The NC will not try to turn on unless there are valid boot files in either the boot partition or an SD. Obviously your boot files are corrupted. Try booting with a bootable SD to see if you can get it to turn on. The battery must also be charged.
Sent from my Nook HD+ running CM10.1 on emmc.
Summary:
I bricked my sister's Nook Color. She bought it refurbished at a pawn shop for cheap and everything was working until I told my sister that I could root the nook and put an android rom on it. My biggest mistake ever.
I looked at a lot of forums relating to the problem and it seems like there isn't a fix. So basically I got to the point of having CWM working.
All was going so well and I decided to flash eyeballer's cm-9-encore-20120904-0700-unofficial.zip on it. The one on Goo.im. After looking at screenshots of CM9 I was impressed.
I did the factory reset on it and wipe the cache, I flashed the CM9 and it was installing and it seem that it was taking a long time and then the nook turned off.
The biggest mistake that I made was that I formatted the boot , I'm a noob, I figured I wasn't the only one so I came across a thread here http://forum.xda-developers.com/showthread.php?t=949699
I thought that CM9 got installed and when I went to turn it on, nothing whatsoever... It doesn't boot no more.
I tried putting the 1gb bootable CWM on a 1gb sd card with Win32 Disk Imager and the Nook didn't boot from the SD card either and I also did the same with an 8gb.
When I go connect the Nook on the computer it searches for a driver called Omap3630 but it doesn't install and it seems to disconnect itself.
I am was looking for more threads and found out that I'm in a similar situation as a user called Jiv_au here,
http://forum.xda-developers.com/showthread.php?t=1146065
3rd post. I also tried what he did with the 8 boot attempts, pressing power button for 60 seconds and pressing the power on, the N and the volumes.
Seakuza said:
Summary:
I bricked my sister's Nook Color. She bought it refurbished at a pawn shop for cheap and everything was working until I told my sister that I could root the nook and put an android rom on it. My biggest mistake ever.
I looked at a lot of forums relating to the problem and it seems like there isn't a fix. So basically I got to the point of having CWM working.
All was going so well and I decided to flash eyeballer's cm-9-encore-20120904-0700-unofficial.zip on it. The one on Goo.im. After looking at screenshots of CM9 I was impressed.
I did the factory reset on it and wipe the cache, I flashed the CM9 and it was installing and it seem that it was taking a long time and then the nook turned off.
The biggest mistake that I made was that I formatted the boot , I'm a noob, I figured I wasn't the only one so I came across a thread here http://forum.xda-developers.com/showthread.php?t=949699
I thought that CM9 got installed and when I went to turn it on, nothing whatsoever... It doesn't boot no more.
I tried putting the 1gb bootable CWM on a 1gb sd card with Win32 Disk Imager and the Nook didn't boot from the SD card either and I also did the same with an 8gb.
When I go connect the Nook on the computer it searches for a driver called Omap3630 but it doesn't install and it seems to disconnect itself.
I am was looking for more threads and found out that I'm in a similar situation as a user called Jiv_au here,
http://forum.xda-developers.com/showthread.php?t=1146065
3rd post. I also tried what he did with the 8 boot attempts, pressing power button for 60 seconds and pressing the power on, the N and the volumes.
Click to expand...
Click to collapse
The problem is that you formatted boot, and CM does not include all of the needed boot files if you formatted boot. You will need to flash the stock firmware back onto the device, and then you can proceed to flash whatever ROM you want on the device, LINK.
I am not sure what version bootable CWM you are using, but download and flash this one,LINK. Since you saw the Omap3630 driver prompt, it does mean that it still is alive and attempting to go through the booting process. As for getting it to boot from this card, you will not get any visual indication that the device is on or not, the screen will stay dark if it’s on or off. Since the device might have been on this whole time I recommend that you fully charge the device before proceeding forward. With no USB cable connected to the device, press and hold the power button for 30 seconds, then insert the SD card, then press and hold the power button for 5 seconds to turn it on. It should boot into the CWM recovery, if it does not press the power button for 30 seconds and try again. It might take a couple attempts, but you should be able to get it. Once you get the device to boot, wipe data/cache, and flash the stock image, and reboot the device. Once you have a working device, you can then boot into the CWM card, and flash the ROM that you want.
GMPOWER said:
The problem is that you formatted boot, and CM does not include all of the needed boot files if you formatted boot. You will need to flash the stock firmware back onto the device, and then you can proceed to flash whatever ROM you want on the device, LINK.
I am not sure what version bootable CWM you are using, but download and flash this one,LINK. Since you saw the Omap3630 driver prompt, it does mean that it still is alive and attempting to go through the booting process. As for getting it to boot from this card, you will not get any visual indication that the device is on or not, the screen will stay dark if it’s on or off. Since the device might have been on this whole time I recommend that you fully charge the device before proceeding forward. With no USB cable connected to the device, press and hold the power button for 30 seconds, then insert the SD card, then press and hold the power button for 5 seconds to turn it on. It should boot into the CWM recovery, if it does not press the power button for 30 seconds and try again. It might take a couple attempts, but you should be able to get it. Once you get the device to boot, wipe data/cache, and flash the stock image, and reboot the device. Once you have a working device, you can then boot into the CWM card, and flash the ROM that you want.
Click to expand...
Click to collapse
You gave me a bit of hope but its not booting. The nook is dead... thanks for the help.
edit: I heard that pressing Power + N is like forcing a shut down so I hold those for 30 seconds and then put the SD card in it No boot.
I tried it again and put the Sd card in it and then press the power button still nothing. I believe this is definitely dead. I wish she had bought it at the B&N store. I think I'm getting her a Nook tablet. I owe it to her.