My holy grail fix for a messed up NC - Nook Color Q&A, Help & Troubleshooting

After pouring thru countless threads, trying to follow different and confusing instructions, clicking on endless dead links and missing files... I finally found success today with an easy fix to restore my NC back to working order (stock). My NC was really screwed up, and files in root were missing-- but this boot image fixed it all. To help anyone else who is having the same issues here are the instructions (hope it will get pinned).
First, check out this Youtube video by Ray Waldo-- http://youtu.be/cmuftsM4xpc
His website is down at the moment where the file you download and create a boot image is.. but I found it listed here on xda in another thread--
http://forum.xda-developers.com/showthread.php?t=1562130 (go to post#8 where you can download the image for the 16gb version)

Are you using a Nook Tablet or a Nook Color? All the info you are providing is for the Tablet... perhaps you have a Tablet and that's why it got messed up in the first place... using NC ROMs on a NT

Related

[Q] just got my nook color looking for some clarity

so i just bought my nook color today and i have some questions, i was searching around in the android development forum and their were about 50 different methods of doing everything.
i am experienced with android and how to do anything just if somebody could post up links in an order i need to follow to be able to get CM7 on to it.
if possible flashing to nand would be preferable but if all we have is SD support thats okay too
thanks for the help guys
also i know i will likely get flamed for this thread but just know i am experienced with android and i have ran it on a non native device before (htc vogue).
My go-to link for flashing CM7 to the internal memory:
http://forum.xda-developers.com/showpost.php?p=11452450&postcount=19
thoughtlesskyle said:
i am experienced with android and how to do anything just if somebody could post up links in an order i need to follow to be able to get CM7 on to it.
if possible flashing to nand would be preferable but if all we have is SD support thats okay too
thanks for the help guys
Click to expand...
Click to collapse
You can get just about anywhere with the nook via two steps:
1) run autonooter for your software version (THIS is for 1.1, obviously for the other versions it will be a different thread)
2) use the market to download ROM Manager, then flash the CWM recovery and download 7.0.2 from the app (or pull a different CWM zip from the forums onto your card if you prefer) and flash.
Simple enough
EpicFail236 said:
You can get just about anywhere with the nook via two steps:
1) run autonooter for your software version (THIS is for 1.1, obviously for the other versions it will be a different thread)
2) use the market to download ROM Manager, then flash the CWM recovery and download 7.0.2 from the app (or pull a different CWM zip from the forums onto your card if you prefer) and flash.
Simple enough
Click to expand...
Click to collapse
thanks, i was reading it from the app so i missed the 2nd part about loading it to my sd card thanks for all the help guys im going to try this now
so i did the rom manager thing picked nook color (old) that might have been the wrong choice but now it wont boot past recovery it just keeps rebooting into recovery
also it wont allow me to flash anything it says i have the wrong prop=encore help somebody
okay got that fixed thanks to one of the tutorials on here (thank god thought i bricked it)
so cm7 is booting now how long does this thing take, mine has been going for like 10 minutes but its not like bootlooping is this just because the tablet builds are huge or do i have cause to be uneasy (nook builds like stock software def didnt take this long)
http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide Just in case
First boot will take 5min+.
Nburnes said:
http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide Just in case
First boot will take 5min+.
Click to expand...
Click to collapse
we are on like 20 minutes now
thoughtlesskyle said:
okay got that fixed thanks to one of the tutorials on here (thank god thought i bricked it)
so cm7 is booting now how long does this thing take, mine has been going for like 10 minutes but its not like bootlooping is this just because the tablet builds are huge or do i have cause to be uneasy (nook builds like stock software def didnt take this long)
Click to expand...
Click to collapse
This isn't your Hero!!! I don't think you can brick this thing.... The Nook always tries to boot from SD before internal memory!!! I had a hell of a time getting CM7 to load originally (at least 10+ minutes). Once you get it loaded, put away that SD card you burned the recovery image too.....Put a new SD card in, install Rom Manager, and flash recovery to it from Rom Manager. Once you get there you can Nand and flash stuff just like you do on your phone.
**Edit** If you get really jammed up, here's the thread on returning to stock unrooted B&N firmware, so you can start over....
http://forum.xda-developers.com/showthread.php?t=914690&highlight=return+stock

[Q] another brick story

I have been working on this for the past few days and for the life of me cannot figure out the problem. I'll start by just laying out a sequence of events.
Bought A500 about a month ago. OTA'd to HC 3.1 4.010.13_com_gen2
Decided not to wait for OTA 3.2 and rooted with iconiabreak.
Did not do a backup (like an idiot, i know)
Flashed Taboonay 2.0 with Thor's 2.1 kernal.
Saw awesome post to get rid of cell standby by deleting phone.apk and telephony.apk....do i did that.
Realize i am an idiot and then run a Nandroid backup.
Was happy for a few weeks when i see that Vache had updated taboonay to 2.1b and decided i wanted to do that.
Downloaded the files and started to flash with CWM. Factory, cache, dalvik wipe. Run Taboonay zip.
Get stuck in bootloop at Taboonay boot screen. $#!t......
Think "it's ok, ill just do an update.zip and go back to 3.1"
Try almost all the files on Vache's full package and update thread.
I put each one on an ext sd card and throw it into recovery boot. The Android guy with gears shows up and it looks like it is going to work.
The progress bar gets about 90-95% of the way when everything just stops. Gears animation, progress, everything.
It then reboots and gets stuck in a bootloop at the android screen. Load a different update.zip and same thing happens each time.
I try to just do a normal recovery boot, but CWM isnt there anymore and i get the ! android.
Normal reboot gives me a bootloop.
So i am stuck and asking if it is the phone and telephony apks that caused everything? if that were the case, how would i be able to load them back up since im totally locked out. I havent tried adb since im out of town for a few days. Thanks for any help that anyone can lend me. Ill try to answer any questions for any information that might be needed.
bumping for great justice~
I've tried decrypting update.zip files and vice versa.
still no luck..
try the fall back to 3.0.1
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.
rorohajj said:
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.
Click to expand...
Click to collapse
Thanks for the reply.
I don't think that will be a viable option for me since i'm not able to get my UID. i've plugged my tablet into the computer and gotten the "hardware found" bubble. It prompts me to look for drivers (which i havent be able to find) and, i assume because it's in a bootloop, wont show up on the computer.
Does anyone know why the update.zip files would fail at 90%? I think that's really the thing that boggles my mind and is most frustrating.
Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.
jeffw111 said:
Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.
Click to expand...
Click to collapse
Unfortunately, no I never plugged my A500 into my computer.
quick update:
I was able to use a different computer and found something interesting.
While trying to transfer or open a decrypted update.zip file, i get an error message saying, "Please insert the last disk of the Multi-Volume set and click OK to continue". Clicking OK just brings it back and i am forced to click cancel.
Anyone have any idea what that would mean??? It doesnt happen when I open or transfer the non-decrypted file. Only the decrypted file using Thor's Acer Update Decrypter application on HC 3.1 and 3.2 files.
While loading the decrypted update.zip on the A500, it almost instantly shows the ! android guy, while the non-decrypted files go 90-95% and then reboot into bootloop.
Any help would be greatly appreciated!
first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.
erica_renee said:
first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.
Click to expand...
Click to collapse
Thanks for your reply, first off.
I'm sorry I didn't make it clear that I had done all of those things during the events of the first post EXCEPT try a different sd card.
So I went out today and bought a PNY 2GB sd card as opposed to the SanDisk 4GB i was using. I formatted it in my Atrix 4G and threw a full update.zip file in there. The first file I tried (from Vache's http://forum.xda-developers.com/showthread.php?t=1113878 thread) was Acer_A500_4.010.38_COM_GEN1 (HC 3.1). Since I was able to open the .zip without decrypting it I loaded it only the sd card. It did the same thing as before (loaded to about 90% then freeze, reboot) except this time I got a "Boot verification failed..." message in bright red letters up at the top left of the Acer screen. Since it didn't work, I loaded Acer_A500_7.006.03_COM_GEN2 (HC 3.2) onto the sd card. Again, since I was able to open the .zip file, I assumed that there was no need to decrypt it. Loaded the sd card and put the tablet into default recovery (not CWM recovery which I no longer have). The same problem keeps happening: it loads to 90%, freezes then reboots. This time, however, it went into a bootloop at the "android" screen.
I've tried decrypted versions of those files, but I always get an error message while trying to open them and when trying to flash them in default recovery, it almost instantly goes to the ! android guy since I'm assuming those files are already decrypted and decrypting them again is bad.
Hopefully if I try enough files, I'll find the one that works...
Until then, if anyone has any ideas as to what I might be doing wrong or should be doing differently, please let me know!
Thanks.
there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.
erica_renee said:
there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.
Click to expand...
Click to collapse
Thanks for your suggestion.
I was able to find my UID from an old CWM backup file and tried this method. I attempted it last night with no success. I was actually in the middle of making a reply saying how heartbroken I was and that I was basically giving up. I decided to try it one more time and made a slight adjustment from my method last night. In the UID file, I had my UID in there as 0x0blahblahblah and kept getting the incorrect UID error in the program. When I tried taking out the first 0x in the program, it gave me an incorrect format error. That is where I was messing up.
Instead of 0x0, all i needed was 0blahblahblah in the UID file.
Attempted the upgrade utility again, and viola! It worked like a champ.
So thanks again to all that helped out and offered suggestions and to all the Devs for their outstanding work. I've definitely learned a lot from this experience.

[Q] Nook Color Firmware v1.4.1 update w/n2acard's cm7.x?

Has anyone attempted dual-booting the new Nook Color v1.4.1 Firmware w/ @Nook2Android cards yet? (announcement from @nookBN on twitter): Nook Color v1.4.1 Firmware Update Now Available for Sideloading
Specifically: Does the new Nook Color v1.4.1 Firmware update lock out n2acard's CM7.x dual-boot feature?
Recommendation: IF already running an n2acard CM7.x dual-booting Nook Color, Do NOT boot into emmc/NOOK until it is safely established and confirmed that you can do so, OR: do NOT allow emmc/NOOK to connect to WIFI as it will be pushed OTA through WIFI this week. Haven't seen anything on n2acards.com forums yet either.
As I rarely boot into emmc/NOOK this won't be too hard for me. Others may need reminding. YMMV.
Updated: NC update v1.4.1 w/n2acards cm7.x?
After catching up on the other Nook Forum threads:
It IS safe to update to Nook Color Firmware v1.4.1.
Just to be safe, I powered down my NC. Pulled my SD card. Did a manual update from my MacBook.
The update copied, updated, booted perfectly afterwards.
CM7 SD card booted aftwards with no problems.
Still a JR member, unable to post links yet. NC Firmware v1.4.1 is at the B&N's NC Software update page complete with instructions. YMMV, but I had no problems. All apps post update on both emmc & CM7 SD card work fine.
It even inspired me to put nookhoney on a separate SD card. It runs fine as well. Have been playing around with the Android SDK on my MacBook, playing with Honeycomb & ICS. Digging into the CM9 alphas to see what's left for an NC build attempt. yay. just sayin'
Hey man, a couple of us have had ClockworkMod reject the update... Did you run into this issue? Mine (same setup) tried to install the rom, showed the little package unzip animation, then an Exclamation point. It then went into Clockwork Mod, and told me that the ROM was unsigned.
Any help would be appreciated.
I didn't run into this. Let me do some digging and see what I come up with. Did you try switching your ROM back to stock, doing the B&N firmware upgrade, then work from there?
Sent from my NookColor using xda premium
obviously i was hoping to avoid that... however I can give it a shot...
I think the main problem is that you got ripped off by N2A
Barnes & Noble Nook Color 1.4.1 fixed for CWM Recovery
Here is a link to the complete Barnes & Noble Nook Color v1.4.1 stock firmware:
http : //www . filefactory . com / file / c0caebb / n / nook-complete-restore-1.4.1.zip
Just remove the extra spaces to reconstruct the URL.
The manifest and updater-script contained within have been updated to work with the install ZIP file function of CWM Recovery. You will not get the error message that the update is unsigned.
Would somebody please mirror the above file somewhere to another host, as it will be gone from FileFactory after 90 days?
Thanks.
ToneDeF71
Hey. I downloaded that file and have been trying to get it to load. Long story short. I was unsuccessful. I was under the impression I didn't have to re-root nook and that all I had to do was copy nook-complete-restore-1.4.1.zip to my nook color or the sd card or something. But I kept running into problems. Are there a set of instructions directly for nook-complete-restore-1.4.1.zip?? Much thanks. Just trying to avoid unrooting, factory stock, updgraeadalskdj ;akld ;akld all the work having to do the work as mentioned above. In short---what am I doing wrong? Much Thanks for any help.
Jbwck said:
Hey. I downloaded that file and have been trying to get it to load. Long story short. I was unsuccessful. I was under the impression I didn't have to re-root nook and that all I had to do was copy nook-complete-restore-1.4.1.zip to my nook color or the sd card or something. But I kept running into problems. Are there a set of instructions directly for nook-complete-restore-1.4.1.zip?? Much thanks. Just trying to avoid unrooting, factory stock, upgrade all the work having to do the work as mentioned above. In short---what am I doing wrong? Much Thanks for any help.
Click to expand...
Click to collapse
Someone else may correct me if I'm wrong here -- you must boot your Nook Color with the Clockwork Mod Recovery utility running from a bootable SD card -- the firmware's .ZIP file should be on that same SD card so that you can access/install it with the utility. That said, because the firmware is to be installed to your Nook Color's internal memory (eMCC), your rooted setup will most likely be overwritten, and then you'll have to re-root your Nook Color after the B&N stock firmware has been verified as successfully installed.
I'm not sure how much effort is involved to back up apps and settings, install the stock firmware, re-root the Nook Color, and then restore the backed-up settings and apps -- it may or may not be worth all the effort.
--ToneDeF71

Installed Overclock kernel now no boot

Hi all,
I messed up my tab (wifi only 10.1) after installing overclock kernel, if i would have looked it was for 3.0 and i was at 3.2, kinda pissed i didnt read comments. Now it boots up an goes to a screen of colored lines. I was told flashing a custom rom would fix this issue, so i downloaded one off this site, but now i have no way of putting the file onto the tablet??? i tried cwm using mount usb storage but i get an error ums lunfile? If anyone has any advice it would really help.
Check the Overcome thread; follow the instructions for "going back to stock." It involves using a program called "ODIN." which you probably used to put CWM on the tab in the first place.
Also, welcome to XDA. This is your first near-brick moment which, unfortunate and stressful now, is a great way to learn that before you do anything you find in these forums you need to read read read!
Thanks for info slack. I found a 3.1 rom that has .tar file for odin. After 9 long hours i realized that odin was the only program that was finding the tab. I flashed that rom just to get it to boot up, then put on the galaxytask rom. Wow what a mess i learned alot this really was my first time doing anything with android. looking forward to learning alot on this site. Thanks again

[HELP] Possibly stuck in APX mode

I'm trying to help this person on reddit but I'm a total noob with the Iconia 500 and after looking at various threads the only conclusion i can come to is APX mode. Could you guys please post a link to the solution or describe them in a noob friendly manner, because I've seen allot of solutions for the APX problem but they're all different, I just wasn't to make sure I find the correct solution for this persons symptoms.
Details-
The Iconia A500 gets to the android logo then nothing.
Attempted update.zip but that doesn't work
Original Reddit post-
Hey, I have an Acer Iconia a500 and it bricked on me. Ive googled the solutions but with no avail. Ive booted in repair mode, ive added an sd card with a new update.zip to the reboot, still nothing. All i get is a little android with an open chest and red exclamation point. Googled the symptoms, but its a really broad subject. I can get it to boot with the SD card for a moment, then a progress bar appears under my dead, open android. The bar doesnt seem to be moving. Im at a loss, could anyone help? Thanks in advance!
http://www.reddit.com/r/Android/comments/1u7rnk/android_tablet_help/
Lekan Adeyeri said:
I'm trying to help this person on reddit but I'm a total noob with the Iconia 500 and after looking at various threads the only conclusion i can come to is APX mode. Could you guys please post a link to the solution or describe them in a noob friendly manner, because I've seen allot of solutions for the APX problem but they're all different, I just wasn't to make sure I find the correct solution for this persons symptoms.
Details-
The Iconia A500 gets to the android logo then nothing.
Attempted update.zip but that doesn't work
Original Reddit post-
Hey, I have an Acer Iconia a500 and it bricked on me. Ive googled the solutions but with no avail. Ive booted in repair mode, ive added an sd card with a new update.zip to the reboot, still nothing. All i get is a little android with an open chest and red exclamation point. Googled the symptoms, but its a really broad subject. I can get it to boot with the SD card for a moment, then a progress bar appears under my dead, open android. The bar doesnt seem to be moving. Im at a loss, could anyone help? Thanks in advance!
http://www.reddit.com/r/Android/comments/1u7rnk/android_tablet_help/
Click to expand...
Click to collapse
No its not stuck in apx mode, just failing to run an update.zip. depends what rom the tab was on and which update.zip was tried.
The solution will require the tabs cpuid so an EUU can be run. If the user does not have a backup of the cpuid and cannot boot into the OS to retrieve it, then it will be no easy fix. Check the cpuid guide in my sig. Linux has to be used unless the user has had the tab connected to his pc at some point then he can use a program called usbdeview to get it. ALL details for these 2 methods are in the cpuid guide.
Once he has the cpuid he can use tge babsector.rar file to reset his tab. This file will install a patched bootloader and custom recovery. All details and download links and instructions are in the root guide in my sig.
He will need full battery charge and a custom ics or jb rom to flash once the babsector.rar file has completed.
As I said this whole process will not be easy. But patience and the ability to follow the steps as they are written will ensure success.
The only thing that may be an issue is if the tab has the dreaded memory chip fault, but babsector.rar file will tell you if this is the case. Acer has recently repaired these faulty tabs even though they were out of warranty.
Good luck
Regards dibb
Sent from my GT-I9300 using Tapatalk

Categories

Resources