Nook Color Stuck on "Loading..." Please Help - Nook Color Q&A, Help & Troubleshooting

I'm posting this because I need some help with my Nook Color. I've had it since August of 2011 and rooted it right away. I didn't have any major issues until this past week when I tried to flash a new ROM. The ROM initially loaded up fine, but when I tried to boot back into recovery to flash GAPPS, as per the instructions of the ROM developer, my Nook got stuck at the "Cyanogen Loading...." screen. It would not get past that point. I held the power button down to shut off, then held the power + N to manually boot into recovery, but it would just stay at "Booting into recovery...." and stay there. I have searched all over the Nook Color section and can not find anything that addresses this issue.
I tried loading ADB, but I can't get my PC to see my Nook to load the appropriate drivers. I was running CWM recovery. I am attaching a few pics of my screen so people can see what I'm talking about.
Any help would be greatly appreciated.
Thanks in advance,
David

Move thread
Please move this thread to Nook Color Q&A. The development section is meant for development threads, not questions about your Nook or troubles that you have.

moved...

bard77 said:
I'm posting this because I need some help with my Nook Color. I've had it since August of 2011 and rooted it right away. I didn't have any major issues until this past week when I tried to flash a new ROM. The ROM initially loaded up fine, but when I tried to boot back into recovery to flash GAPPS, as per the instructions of the ROM developer, my Nook got stuck at the "Cyanogen Loading...." screen. It would not get past that point. I held the power button down to shut off, then held the power + N to manually boot into recovery, but it would just stay at "Booting into recovery...." and stay there. I have searched all over the Nook Color section and can not find anything that addresses this issue.
I tried loading ADB, but I can't get my PC to see my Nook to load the appropriate drivers. I was running CWM recovery. I am attaching a few pics of my screen so people can see what I'm talking about.
Any help would be greatly appreciated.
Thanks in advance,
David
Click to expand...
Click to collapse
The problem is you are in a recovery bootloop and your recovery is missing or corrupted. Go to my tips thread linked in my signature and look at item A8.
Sent from my Nook HD+ using Tapatalk

leapinlar said:
The problem is you are in a recovery bootloop and your recovery is missing or corrupted. Go to my tips thread linked in my signature and look at item A8.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
Thanks...I appreciate it...as soon as I get to a computer I will explore it fully....thanks again
Sent from my EVO using xda app-developers app

Related

I'm sorry XDA, but I need help with dual booting my Nook Color :(

I've spent a couple days trying, I've searched the forums and Google'd any issue I ran into, but I think I am just doing something wrong here. As a last resort, I'm making this thread to ask for your help.
I am having the hardest time getting my Nook Color (blue dot) to dual boot correctly. I can get it to boot into C7 just fine, but when I try booting to the stock Nook Color (alternate boot?) it just hangs at the screen with the logo and "alternate mode" in text.
I'm following this guide:
The Very Corrected CM7 & Stock 1.2 Dual Boot Guide
I have a CWM SD card with the corrected 1gig image with CWM 3.2.0.1.
I have the two new partition files to correct the blue dot changes on my Nook.
I have Cyanogen Nightly 138.
I have downloaded all the files that the guide mentioned.
I can root it successfully and get rooted Nook Color, and I can install C7 over it and have it run fine. Dual booting is a different story and is giving me a headache
In the guide, I have tried using the included u-boot file, which unfortunately didn't work. I have also tried with and without correcting the blue dot partition change.
I then reinstalled C7 to use the default boot method (the one with the menu) and I was able to get into C7. But holding the volume buttons to boot to stock causes the Nook to hang.
Am I doing something wrong? Any help will be really appreciated.

Is my nook color forever bricked? Flashed nook tablet firmware like a goon..

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.

[Q] Nook Color Not Working, Just Black Screen

Someone help! I rooted the nook color using cm7, and then I tried to do a reset back to the factory image (8 power on/off's), and then it got stuck in a loop saying it was downloading software, and now it will not power up at all unless I use a bootable sd card. I have tried using restore files, files direct from the Barnes & Noble website, and nothing I can do seems to make a difference. It is driving me crazy. The screen just stays black, and the only indication of life that I get is if I have it plugged into my computer, and I hold the power long enough, a box pops up asking me to choose where to connect the new device, but nothing shows up on the screen at all. I am going nuts with this thing, and the threads that I have found on here about it have had all of the files taken down. Any help with this would be greatly appreciated, and thank you in advance.
dvdchancellor said:
Someone help! I rooted the nook color using cm7, and then I tried to do a reset back to the factory image (8 power on/off's), and then it got stuck in a loop saying it was downloading software, and now it will not power up at all unless I use a bootable sd card. I have tried using restore files, files direct from the Barnes & Noble website, and nothing I can do seems to make a difference. It is driving me crazy. The screen just stays black, and the only indication of life that I get is if I have it plugged into my computer, and I hold the power long enough, a box pops up asking me to choose where to connect the new device, but nothing shows up on the screen at all. I am going nuts with this thing, and the threads that I have found on here about it have had all of the files taken down. Any help with this would be greatly appreciated, and thank you in advance.
Click to expand...
Click to collapse
Look in my tips thread linked in my signature. Look at item A15 and it tells you how to download and flash with CWM the latest stock rom.

[Q] Nook Color Bricked?

have a nook with CM7 installed on it. was going return my nook to stock to give it to my little sister, but when i went to install the stock stuff back on it got stuck in a loop. It won't boot from an uSD card with clockwork on it and when I tried the 7 hard boot in a row trick, it didn't do anything. Did i really brick the thing? or can it be recovered?
I attached to shots of the screen i get when i power it on normally and the other when i try to go into recovery mode.
I answered that in the other thread that you posted the same question on.

[Q] A500 Boot Issues...need assistance

I've searched and found a few similar (not identical) problems that people were having, and tried some of the solutions, and none have worked.
I'm trying to fix this stock Acer A500 for a friend. It will boot up part way, goes past the acer screen and android screen, but then stops at a black screen with 'android system' in the upper left corner, the home and back buttons in the bottom left, and the time, signal, and battery life logos in the bottom right. Then there's the Power Off thing in the center of the screen, and it says shutting down but it never shuts down.
I boot into the stock recovery mode, and it says in the upper left on the acer screen:
erasing cache before SD update
SD update cmd: recovery
--update_package=sdcard:update.zip
booting recovery kernel image
then it shows the android with the turning gears, then goes straight to the android with the warning symbol.
Since I can't get into the OS, i have no idea which version or specific model this is, but i downloaded a few different honeycomb update.zips, and put those on the SD card, and when i tried booting with those, the loading bar pops up under the android logo, and it goes to about 1/3 of completion before switching back to the warning symbol.
I tried downloading what im pretty sure was a full version of jellybean for this tablet, and it went straight to the warning symbol, no loading bar. same when i tried renaming the file update.zip >.>
im clearly very new to all this, but i'd really like to get this thing working.
is there a way to do a factory reset without booting all the way into the OS?
im not sure because it seems like the only file its looking for in recovery mode is update.zip.
if anyone has any bright ideas, id appreciate the help.
Also, not sure if this is relevant, but when i boot it normally, and it goes to the 'shutting down' screen, the battery level indicator says its almost dead, but i can leave it plugged in for hours and nothing changes at all.
EDIT: Also, it won't even boot if the power cable is not connected.
Similar issue hope there is a solution
I have a similar problem. Tablet was working fine, sitting on docking station. Returned to it the next day and when I went to wake it, it would not wake. Rebooted it but will not reboot. Sits on the ANDROID screen after the ASUS title screen indefinitely. If I try and boot into recovery it fails at "update.zip" and I see the broken Android image laying there.
Is there a means to restore it from PC via the usb cable and can someone please post a very noob friendly walk through step-by-step?
Greatly appreciate any positive advice!
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
zardoz99 said:
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
So, dead chip? So soon? Nice.
NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
Yep.. 14 months old in my case. Contacted Acer and said "what about a fix?" They said, "no chance unless you cross our palms with lots of silver."
So, bought a Samsung Note 10.1 instead. Acer can "stuff it". I won't be buying a tablet from them again. Considering that I bought their "flagship" product of the A501 with the 64GB memory, this is truly unacceptable.
I was incredibly careful with it and certainly never did anything to void the warranty. But, you only get 12 months and then it's over.
NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
skurtov said:
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
Click to expand...
Click to collapse
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
NoOneSpecific said:
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
I'll have him PM you when he is able.
Thanks!
skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
coluwyvurne said:
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
Click to expand...
Click to collapse
You are quite right sir, however the button combination I am most familiar with is holding the power and the reset button (the one you have to stick the paper clip in) when you first start it up. It should then either say APX mode on the screen or be blank, either way the computer will identify it as a APX device and automatically install the drivers.
Going into APX MODE manualy
You enter APX mode by holding down the Reset button(with paper clip). Do not release it. Hold down power for 3 secs and then release it. After another second, release the reset button.
Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
The screen of your tablet is black.
Quoted from Civato
Click to expand...
Click to collapse
The next course of action is to get the SBK, from what it sounds like the tablet didn't write a partition properly and that's why it's not booting. So what you can do is wipe out the partitions and install a custom bootloader and recovery. Not only does it fix things but it also opens up his world to custom roms . Okay, back to the matter at hand, I don't know if he has his SBK or not, and if he does skip the step to find it and just run babsector below. If not then follow the next step.
You'll have to pull the UID from the tablet using this method described here:
http://git.pappkartong.se/?p=a500/apxuid.git;a=snapshot;h=HEAD;sf=tgz
There's a readme
After getting the UID and calculating your SBK you'll just go to the next step.
All credit goes to user eppeP.
Click to expand...
Click to collapse
Run this file hosted here:
http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
And this file basically rewrites and formats the partitions out installs a custom bootloader and recovery
Credit goes to Danny2 for finding this and posting it.
Click to expand...
Click to collapse
Once this is done, pick a new rom. I prefer the Civato ones, load it on a SD, boot to recovery, erase dalvik cache, cache, do a factory reset wipe (from the recovery menu!), then wipe system, flash the rom and go on your merry way
Many thanks for the reply.
As per your instructions, I have booted the tablet into APX mode. However, as I do not know the UID of the device, I've had to try to run the utilities to create a driver for the device and then pull UID from the tablet...
I am able to create the driver for the device and install it with driver signing off in Windows, but I can't figure out how to run the script to get the UID. I notice the file in the package you directed me to contains an .SLN file, which would indicate it is a programming solution file. I have Visual Studio on my system but it cannot open this particular .SLN file.
How would I run what's in the package to pull out the UID of the tablet?
Any help getting past this hurdle would be much appreciated!

Categories

Resources