Database Develop

B&N Announces 1.3 update on FB

Just wanted to get the work out that B&N announced on FB this morning (18 minutes ago as I post this) that there is a 1.3 upgrade to the NC.
From the B&N Community link on FB:
Starting today, NOOK Color owners have access to firmware version 1.3, a software update that enhances the best-in-class NOOK Newsstand by offering even more interactive versions of the country’s favorite magazines and newspapers.
Not only does this update offer access to new bestselling titles including People, Time, Sports Illustrated, Fortune, Parents and Fitness magazines, the new capabilities allow for Special Interactive NOOK Editions with enhanced content—like videos, audio podcasts, animations, photo galleries, and more—for select titles. Plus, print subscribers to People, Time, Sports Illustrated and Fortune can enjoy the NOOK Magazine™ versions on their NOOK Color at no additional cost.
Also included in the update are performance improvements and new features.
NOOK Color customers can enjoy these new features through a free software update available at www.nookcolor.com/update or provided over the air (OTA) to customers connected to Wi-Fi beginning this week.
For more details about this update, please read the full press release here.
Click to expand...
Click to collapse

Okay, I have an interesting situation...
I purposefully installed CM7 on a uSD (using verygreen's guide) to keep my NC stock while I am in my warranty and for other reasons.
At some point however, I must have used CWM's (ROM Manager) feature to Flash CWM Recovery. I know this because when I follow B&N's instructions to manually update to 1.3 the NC reboot's into CWM (I had previously removed my uSD with CM7 on it so there would be no trouble with the update process).
When the NC boots into CWM, it is with errors that it does not find a "signed" zip file and I can only reboot (which reboots back into the stock ROM just fine).
I haven't had much time (as I'm at work at the moment) to investigate this so my question is...does anyone know how to remove CWM that has been installed from the "Flash CWM Recovery" feature in ROM Manager? Or is there a way to bypass CWM during the 1.3 update process?
I was hoping to have this on 1.3 so I could play with it at lunch
Any ideas?
P.S. I am hoping to be able to remove CWM without resorting to flashing a new stock ROM if possible....

cdaters said:
Just wanted to get the work out that B&N announced on FB this morning (18 minutes ago as I post this) that there is a 1.3 upgrade to the NC.
From the B&N Community link on FB:
Click to expand...
Click to collapse
You are a little late.... http://forum.xda-developers.com/showthread.php?t=1231136

patruns said:
You are a little late.... http://forum.xda-developers.com/showthread.php?t=1231136
Click to expand...
Click to collapse
Saw that after I posted...I guess I'll have to follow them on twitter, heh

fwiw, I just loaded the stock rom over the top of my stock rom that had CWM flashed to the eMMC.
I wish that CWM had a feature to "un-flash" and that locations were not hard coded in the app (because it seems that it wants to install to eMMC every time) so it could be used interchangeably with the eMMC or a uSD installation of custom ROMs.

Perhaps verygreen's instructions should be updated. I have seen far too many people who ended up with custom coding on their eMMC and that is definitely a no no..... verygreen has not posted in over a month though he has been here.....

patruns said:
... verygreen has not posted in over a month though he has been here.....
Click to expand...
Click to collapse
Yeah. I had PM'd him regarding his installer a while ago but he has not responded either...he has fallen into "lurker mode"
I don't even know what I was thinking when I flashed it, probably just to see what it did with regard to running from the uSD more than anything else. I had previously been using CM7 on the eMMC before I went the CM7 from the uSD route.
Verygreen very clearly outlines the update process though if we just read his guide. I'll be the first to admit that I usually skim through things and jump right to it, heh, I am sure others do this too. So I can see where it is easy to miss. Even seasoned IT people like me miss things.

[Q] Bootloader question and ROMs other than CM

When I originally got the TouchPad I played around with just long enough to put CyanogenMod on it then gave it to my parents. Here is the info I got from the device:
Modboot version 0.3.5 (Dont recall the actual version.. I recall seeing something like this)
ClockworkMod version: 5.0.2.6
CyanogenMod version: Alpha 2
Since then I personally got a Galaxy Nexus and have ventured into the world of ROMs. One of the first things I did when I got a hold of the TP again was to install GooManager then browse by compatible ROMs. To my surprise I saw that Black Ice (my fav ROM) was also available in a Tenderloin version which GooManager said was compatible with the TP so I did a Titanium backup and a nandroid backup then wiped back to factory, wiped the cache and wiped the Dalvik cache and flashed Black Ice.
First thing I noticed was that there was now another entry in the boot list named "Black Ice" but it didnt work or do anything. Choosing the original CyanogenMod option did boot Black Ice (after showing a brief CM logo which I assume is part of CWM?). However once booted into Black Ice I wasnt able to get the Wifi to turn on at all. It would flip the toggle but it would just grey out and never actually turn on. Naturally I did a nandroid recovery and its all back to the way it was but it left me with some questions...
1) Does the TP have to be dual-booted with WebOS? Or can I set it up similar to my GNex and have it not prompt for a boot option and run only Android?
2) Should all "Tenderloin" builds work on a TP? And if so what is the proper method for me to switch to a different ROM? The method I used above is what I do for my Gnex but I realize it might be different on TP.
3) Did I do the flash properly and it should have technically worked and the wifi issue i had is fixable?
Thanks for any input!

WoodroweBones said:
When I originally got the TouchPad I played around with just long enough to put CyanogenMod on it then gave it to my parents. Here is the info I got from the device:
Modboot version 0.3.5 (Dont recall the actual version.. I recall seeing something like this)
ClockworkMod version: 5.0.2.6
CyanogenMod version: Alpha 2
Since then I personally got a Galaxy Nexus and have ventured into the world of ROMs. One of the first things I did when I got a hold of the TP again was to install GooManager then browse by compatible ROMs. To my surprise I saw that Black Ice (my fav ROM) was also available in a Tenderloin version which GooManager said was compatible with the TP so I did a Titanium backup and a nandroid backup then wiped back to factory, wiped the cache and wiped the Dalvik cache and flashed Black Ice.
First thing I noticed was that there was now another entry in the boot list named "Black Ice" but it didnt work or do anything. Choosing the original CyanogenMod option did boot Black Ice (after showing a brief CM logo which I assume is part of CWM?). However once booted into Black Ice I wasnt able to get the Wifi to turn on at all. It would flip the toggle but it would just grey out and never actually turn on. Naturally I did a nandroid recovery and its all back to the way it was but it left me with some questions...
1) Does the TP have to be dual-booted with WebOS? Or can I set it up similar to my GNex and have it not prompt for a boot option and run only Android?
2) Should all "Tenderloin" builds work on a TP? And if so what is the proper method for me to switch to a different ROM? The method I used above is what I do for my Gnex but I realize it might be different on TP.
3) Did I do the flash properly and it should have technically worked and the wifi issue i had is fixable?
Thanks for any input!
Click to expand...
Click to collapse
1) yes you have to keep dual boot. A quick search would have given you this info. But when you install android it should default to boot Android in moboot... if you have several entries then I suggest you clean moboot or wipe android from the TouchPad altogether and start off with a cleean install (the stickies have plenty of instructions on how to do any of that
2) tenderloin is the codename so to speak for the TouchPad. You need to read up on the workings of moboot to understand the dual booting method and understand the entries you see when its booting and how to manipulate it (again information readily available on the forum)
3) yes you flashed correctly but your moboot /boot folder has conflicting entries. Most wifi issues have been fixed in all the most stable ROMs. Your issue may be related to conflicts from your install and/or having one of those.devices that is.just persistently going to have android wifi issues. When i say devices I mean yours in particular. Some of us depending on our device have never had issues no matter what ROM we used
Hope that helps...
Sent from my cm_tenderloin using Tapatalk 2

As abrasive as always...
Anyways, he does have a couple of points.
1) Yes, you do have to keep the dual-boot setup. You can change the default to whatever you want, or you can clean it up. There are some nice topics that explain it all throughout the General and Q&A and Dev forums (I don't have them handy). If you want to default to one of those, I can tell you now you need a little bit of familiarity with terminal (which is easiest), or you need to boot back into WebOS, install Preware, and then install CyBoot (which changes boot options).
2) He's right, Tenderloin is the name given to the Touchpad, like es209ra is the name for the Sony Ericsson Xperia X10. It's just what it's called.
3) Wifi issues are something that are hit-and-miss with a lot of people. One thing that seems to fix a lot of peoples' issues is switching your router to one of the lower channels (1-6) rather than the upper (6-13). There's also usually a lot less chatter on the lower 1-3 than closer to 6 (which is the default). Also, set your wireless to WPA2/Personal with AES (no TKIP), and disable WPS (Wireless Protected Setup). This will make your network more secure, and work better with your TP.
3) Another thing I've noticed is that if you switch your Wifi off and then back on, it can take upwards of a minute before it's re-enabled. Not sure why, but it is something to note.
Hope that helps you with a little less attitude than our resident... person... posted above.
Cheers.

Thank you ve6ay!
I was pretty positive Tenderloin was meant for touchpad but was thinking maybe its for actual android tablets only.
For some reason with Black Ice I just could never get the Wifi to enable at all. The latest AOKP nightly wouldnt even flash but I ended up getting AOKP Milestone 5 to flash and its working great! Have definitely experienced the other "normal" wifi issues of losing connectivity and having to switch to airplane mode and back, etc. so I am used to those already

Having a problem with registering my NOOK HD+

Just bought a used NOOK HD+ on Cragslist, but the page shows this device has been registered by another user.
In fact, all previous user data and information were removed from this tablet. I was wondering if all NOOK tablets can be registered once only?

cenbit said:
Just bought a used NOOK HD+ on Cragslist, but the page shows this device has been registered by another user.
In fact, all previous user data and information were removed from this tablet. I was wondering if all NOOK tablets can be registered once only?
Click to expand...
Click to collapse
Unfortunately, in some cases Nook's can only be registered once. However certain Nooks can be registered more than once; which are some of the elder builds. I've had this problem before, and when contacting Nook, they couldn't assist either. However, I was able to recall the e-mail used to register the device; as my father registered it, and not myself.
I'm sincerely sorry to say this, but the Nook in some cases can only be registered once. You could try contacting Nook and tell them that you can't register your device. Perhaps they could offer you a replacement device under warranty? I'm unsure.
Although, if you're going to run CyanogenMod on your Nook, and not use the Stock ROM; you do not need to register your device. If you install CyanogenMod, you will "bypass" the registration process. If you're wondering what CyanogenMod is, it's basically a close enough experience to a stock Android build. The stable CyanogenMod (CM) 10.1.3 runs Android 4.2.2 which is more recent than the stock ROM on the Nook, which runs 4.0.4.
It's completely up to you however. If you don't want to use the stock ROM, and want to keep the device, instead of having it replaced; you could install a stable version of CyanogenMod. Of course, and again it's completely your choice.
I'm sorry about your issues, and all the best.

HiddenG said:
Unfortunately, in some cases Nook's can only be registered once. However certain Nooks can be registered more than once; which are some of the elder builds. I've had this problem before, and when contacting Nook, they couldn't assist either. However, I was able to recall the e-mail used to register the device; as my father registered it, and not myself.
I'm sincerely sorry to say this, but the Nook in some cases can only be registered once. You could try contacting Nook and tell them that you can't register your device. Perhaps they could offer you a replacement device under warranty? I'm unsure.
Although, if you're going to run CyanogenMod on your Nook, and not use the Stock ROM; you do not need to register your device. If you install CyanogenMod, you will "bypass" the registration process. If you're wondering what CyanogenMod is, it's basically a close enough experience to a stock Android build. The stable CyanogenMod (CM) 10.1.3 runs Android 4.2.2 which is more recent than the stock ROM on the Nook, which runs 4.0.4.
It's completely up to you however. If you don't want to use the stock ROM, and want to keep the device, instead of having it replaced; you could install a stable version of CyanogenMod. Of course, and again it's completely your choice.
I'm sorry about your issues, and all the best.
Click to expand...
Click to collapse
Thank you for your feedback. It's very detail. Now I am very interested in CyanogenMod you mentioned. But I am not familiar with this.
I'd like to know if I still can return to the stock ROM after I installed the CyanogenMod ROM.

Yes, you can go back to stock, but you still cannot register it unless the original user deregisters it. Since you bought it on Craig's list, can you contact the previous owner and get their screen name and password? Or maybe they can call B&N and deregister over the phone.
Sent from my BN NookHD+ using xda premium

cenbit said:
Thank you for your feedback. It's very detail. Now I am very interested in CyanogenMod you mentioned. But I am not familiar with this.
I'd like to know if I still can return to the stock ROM after I installed the CyanogenMod ROM.
Click to expand...
Click to collapse
No problem at all, and I do apologise for the inconvenience being caused to you, as a result of not being able to register your device. I'll do all I can to assist.
After you install CyanogenMod, you can always return to the stock ROM; by formatting/erasing everything on your Nook and installing the default/Stock ROM back on (don't worry, it's easy and fun). If you want, you can try installing the stock ROM provided by leapinlar (another developer/great contributor here at XDA) over your current setup, and perhaps you maybe able to register you device then. I flashed the stock ROM provided by leapinlar for a friend, and he was able to register with a new Nook account (although he did own the Nook from new). Or, perhaps you could try this:
Turn off your Nook;
Turn on your Nook;
Immediately after turning on, and you see the text "Nook", hold the power button until the device turns off;
Do the above steps eight (8) times.
Make sure you keep a note of how many times you have done the above, to ensure you have actually turned off the Nook 8 times. What doing the above will do is, it'll reset your Nook. After that, you can try registering it then and hopefully it should work. Sorry I didn't mention this earlier, it didn't occur to me. If it doesn't work, you can try installing CyanogenMod (CM) or try installing the Stock ROM again.
You can install CyanogenMod, which is basically a full Android 4.2.2 setup (later versions of Android are currently being tested/developed for the Nook). With CyanogenMod you do not need to register with Nook, and you can begin using your Nook after installation. However with CyanogenMod, you will need to register with Google and optionally with CyanogenMod. Once you register with Google, you can access all Google services such as Google Play (the app store). The optional CyanogenMod registration allows you to monitor your devices and such.
If you'd like to install CyanogenMod, or try reinstalling the stock ROM, you must have an SD card. The SD card must be blank, and you must be able to connect the SD card to your computer, so you can write to it directly. I would recommend a minimum of 4GB SD card capacity, but if you have anything else laying around, I guess we can make do with it. The absolute minimum you require to install CyanogenMod/Stock ROM is 2GB.
If you'd like to install CyanogenMod, please see this guide: http://forum.xda-developers.com/showthread.php?t=2317500
When downloading the CyanogenMod file, ensure you download this version: http://download.cyanogenmod.com/?device=ovation&type=stable which is a stable version, ready for everyday use.
After following the guide I have just linked to above, you should have CyanogenMod running on your Nook perfectly fine. If you have any problems, please let me know, or post in the above thread.
Before you try CyanogenMod, if you would like to try "fixing" the stock ROM (i.e. see if you can register) by installing the stock ROM again, overwriting your current setup, please reply here and I will detail how to reinstall the stock ROM and reset it, which should hopefully allow you to register the device.
All the best.

[Q] HD+ Stock (CWM + root) Vs. CM which better?

Hello all.
I have a virgin HD+, so far i just enable unknown sources. At this point in time i want to go further. I really don't know what good things and limitations will introduce CM and thats why i think i might be better just to root it.
What are the suggestion go and change the OS completely or just root?
What i see good
Root:
more apps and good mods while staying original
CM:
USB OTG + root + full android
Thanks

ceag235 said:
Hello all.
I have a virgin HD+, so far i just enable unknown sources. At this point in time i want to go further. I really don't know what good things and limitations will introduce CM and thats why i think i might be better just to root it.
What are the suggestion go and change the OS completely or just root?
What i see good
Root:
more apps and good mods while staying original
CM:
USB OTG + root + full android
Thanks
Click to expand...
Click to collapse
Use both to start make a bootable CM sdcard and have stock on internal then you can decide which one you like better. I personally would go with a Custom Rom it is much faster that way.

I had my HD+ unrooted on stock for week and could not stand the speed. Apps crashing constantly, extremely sluggish behavior; I couldn't stand it. I didn't have a micro to full size SD card adapter, so I ordered one of off Amazon. I rooted and then tried every ROM available for our Nooks. I think CM11 runs best.

Flash Player based reboots. Yes I know it doesn't support flash....

My niece's Nook had the 99% bug with stock Nook HD ROM. I was tasked with fixing it, and figured why not put a custom ROM on it.
I tried Carbon ROM first, now I'm on CM 10.2.1. Both ROM's exhibit the same behavior. She would go to a website with pop-up ads and flash images and the thing would reboot by itself. With Carbon ROM she couldn't even play app store games, but CM seems to have fixed that at least.
I tried Dolphin and Fire Fox and both would allow the thing to run those websites or flash based stuff without reboots. After a few hour though it would reboot again...
I saw another post with the same symptoms, so I have looked. I have Googled the heck out of this issue and see no fix.
Here is the other post: http://forum.xda-developers.com/showthread.php?t=2778338
Any insight would be appreciated, thank you

Since flash mobile has been deprecated, you get what you get. It is highly temperamental. Blame Apple, Adobe or whoever but there's little you can do about it unless you want to give Adobe billions to support flash mobile again or just uninstall it.
That said, the device may still reboot with or without flash installed.

It's gotta be a narrowed problem seeing as how there's not 500 posts with the same issue, it doesn't seem widespread.
I can only assume that the stock HD ROM blocks it entirely somehow unlike AOSP.
I know on the old Nook color you could have stock and just remove the B&N UI and have it look like AOSP, but I can't find a similar option for the Nook HD