Database Develop

[warning] ota update!!!

So today I was at work and a little notification popped up about a software update. I just left it alone and went on with work. I come back from lunch and it updated itself and disabled all my apps and root. The SD nethod with Nooter does NOT work. The software version showed 1.0.1. I ended up returning the Nook as its pretty useless with no root & 3rd party apps for me. I will be waiting and seeing where this all pans out as more people get the OTA. Good luck!

houseofbugs said:
So today I was at work and a little notification popped up about a software update. I just left it alone and went on with work. I come back from lunch and it updated itself and disabled all my apps and root. The SD nethod with Nooter does NOT work. The software version showed 1.0.1. I ended up returning the Nook as its pretty useless with no root & 3rd party apps for me. I will be waiting and seeing where this all pans out as more people get the OTA. Good luck!
Click to expand...
Click to collapse
I haven't gotten any notification of an update and I've been using the wifi all day. Don't see anything about an update on the Barnes and Noble site or community forums.
Not saying it doesn't exist. But if so, it's quite odd for them not to officially announce it the way they do for the original Nook firmware updates.
Keeping my WiFi off for the time being though.

This is definitely not good news. Can someone else confirm this firmware update ? B&N is not showing any updates on their website and the community forum over there is not indicating anything either. Haven't heard anything over on MobileRead.com forums either. I'd imagine that someone else would've gotten this update by now (either rooted or not) and reported it.

I'm wondering if mine just happened to get caught in a glitch in their system. Like how some Android phones got updated randomly before others. Your guess is a good as mine. I guess we will see if anyone else got hit too.

Any idea of where it saved it to? If this comes down the pipe, I'd like to pull it apart for a look at what they did

Those bastards

Maybe its time to edit the host file to prevent NC from calling home?
Sent from my SPH-D700 using XDA App

jimmyz said:
Maybe its time to edit the host file to prevent NC from calling home?
Click to expand...
Click to collapse
Do we know what domain the updates are coming from?
There are some instructions for blocking updates here:
http://forum.xda-developers.com/showthread.php?t=860480
But as the author says, they may not work (read the thread).
The best option is to flash a new rom probably and it looks like good progress is being made there.

houseofbugs: Did you get a notification before reboot? My guess would be that these updates are installed from recovery, so there may be an interim solution to delete the file from internal memory if you get a notice.
Far from perfect, but better than nothing.

So nobody else has received this update ? I Googled for any info, checked out the BN forums and another forum dedicated to the NC and nobody else has reported any kind of software update.

Just as a precaution I called my gf and had her turn off my nook and turn off wifi on hers, not looking forward to going home and finding root has been broken. Don't like the fact that it force updates itself without user interaction too, from what I gathered from the op's post. OTACerts.zip doesn't do anything on the nook?

ZeroSX said:
Just as a precaution I called my gf and had her turn off my nook and turn off wifi on hers, not looking forward to going home and finding root has been broken. Don't like the fact that it force updates itself without user interaction too, from what I gathered from the op's post. OTACerts.zip doesn't do anything on the nook?
Click to expand...
Click to collapse
If the Op didn't mess with the OTACerts.zip, then we wouldn't know. Op, did you disable updates as suggested in the thread above?

I haven't seen any "update" messages on mine. I double-checked and my NC is still running version 1.0.0. My wifi has been on for the past couple days (including all night last night) and I've seen nothing suggesting a firmware update.
Maybe I'm lucky. Looks like B&N may be planning to force a firmware update soon. It'd be nice if they gave us the option to decline it (they'll probably strip in-Store features without the most current version, but I've read here that rooting does away with in-Store features anyway).
There's another thread over in NC Android Dev where someone got a firmware update scare. Looks like a false-positive, but it's something to keep us on our toes.

Hmm no updates here either..

nothing...

I remember reading that someone else got an Update Available notification in the huge thread that started this forum. I think they said they did a system restore to factory and it allowed them to re-root it, but I don't recall if it had a version number in it. Same thing happened, nobody knew what was going on.
Regardless, we should eliminate the ability for B&N to apply automatic updates at will.

After un-rooting and resetting back to factory fresh settings, the Nook DID download an update, version 1.0.0.0. The notice appeared in the notification area.
The good news is that I am still able to root using the nooter method.

gojeda said:
After un-rooting and resetting back to factory fresh settings, the Nook DID download an update, version 1.0.0.0. The notice appeared in the notification area.
The good news is that I am still able to root using the nooter method.
Click to expand...
Click to collapse
That's not an update, it's an improper notification. It hasn't been *updated* to anything, since that's what it came with stock. It's just the nook's way of saying it's been reset to defaults.

Hopefully the update is not rolling out...
...but if it is I hope it hits my NC after this weekend when I have to take my son from the USA to the UK! Two flights and two airports without Angry Birds to keep him happy would be unpleasant.

Hmmm...
OTAcerts.zip would be my usual suggestion, for this kind of thing.
If anyone gets the nook with the update, try and grab the URL of the update via logcat.
Failing that, someone with the update might need to try things to get it rooted RageAgainstTheCage, anyone?
I don't know what you specifically need for the nook to let you sideload etc, but RageAgainstTheCage would make sense to work and get at least shell root.

Read to me not working with 1.0.1 update?

My NC was updated OTA this morning to 1.0.1. I noticed after the update that the Read to Me functionality doesn't work. I get an error and have to force quit and even if the book loads up correctly, it doesn't read. Have already checked volume levels and such.
Here's the error:
"Activity Fava Book Reader (in application Fava Book Reader) is not responding."
Anyone else seeing this or know about this issue?

I've been having the same problem. Rooted on 1.0.1. I saw another post for a non-rooted NC that was having the same issues too.
http://bookclubs.barnesandnoble.com...o-Me-quot-books-not-reading-to-me/td-p/760638

I'm rooted on 1.0.1 using Auto-nooter and Read To Me works fine.

I'm on 1.0.1 and rooted with Auto-nooter 2.12.18 - Read To Me doesn't work anymore for me either. Any ideas?

barbo said:
I'm on 1.0.1 and rooted with Auto-nooter 2.12.18 - Read To Me doesn't work anymore for me either. Any ideas?
Click to expand...
Click to collapse
1.0.1 broke my read me functionality BEFORE I even rooted. That's why i've avoided it. My kids like using that.
Sent from my XDA app on my Nook Color

When your read to me function broke, had you side loaded the 1.0.1 update or was it the ota? Mine was sideloaded and I'm thinking that the 1.0.1 update file was some how corrupted when I downloaded it. On Christmas day, when a ton of people got a NC for Christmas and bogged down the BN website, is when downloaded the update file. So I might wipe and use a different source or a fresh download from BN.

willywayne said:
When your read to me function broke, had you side loaded the 1.0.1 update or was it the ota? Mine was sideloaded and I'm thinking that the 1.0.1 update file was some how corrupted when I downloaded it. On Christmas day, when a ton of people got a NC for Christmas and bogged down the BN website, is when downloaded the update file. So I might wipe and use a different source or a fresh download from BN.
Click to expand...
Click to collapse
mine was OTA. i hadn't even rooted it yet. i was just playing with the stock device and then it updated and the feature was gone. just kept erroring out and freezing up or pulling up the book but not reading.

Alright, I completely reset to stock (8 reboots and de-registered it). Checked the info and was back to 1.0.0. Tried the "read to me" function and it worked fine. Put it to sleep waited a few minutes woke it up and tried again with no problems. Side loaded a fresh download of the 1.0.1 update and let it update. Tried the "read to me" again and it worked fine. Put it to sleep and waited about 15 minutes and now it is broke again.
My wifes has had hers since Christmas too, updated it to 1.0.1 the same day as mine and hers still works perfectly.
I will be going to Best Buy to exchange mine for a new one in about ten minutes.

Did you check to see if any other audio was working after the 1.0.1 update? Other as in other than Read to Me?

eyecrispy said:
Did you check to see if any other audio was working after the 1.0.1 update? Other as in other than Read to Me?
Click to expand...
Click to collapse
I thought maybe you were on to something because I had sound turned off in a game. I turned it on in the game and it worked but still not in the "Read to Me". (1.0.1 update plus nootered)

I never could get the audio on Pandora to work but I have it on my phone so I never put much effort into it.
I just got back from Best Buy, updated my new NC to 1.0.1 and everything is working now, including Pandora. I will let it go for a couple days before I root it to make sure everything still works.

FWIW, I turned up my volume to nearly max and Read to Me was working. I wonder if it was a simple volume mistake or if somehow something was changed. I hope everyone else's problem is solved as well

[Q] Odd Nook Color problem

I have done some research here and on Google on a really odd problem...
My wife has a NC I updated to 1.0.1 then rooted. About a week later on her way to work it restarted and unupdated (?) back to 1.0.0... So I thought it was a fluke, root was gone but most things still worked, not Youtube or market but other apps I installed while / did.
Now twice, 2 days in a row I have checked out the device, I installed Clockwork, did a backup and the next morning on the way to work (She works in manhattan, takes the train in) it is bootlooped "touch the future of reading" so last nite I ran the clockwork restore and it was fine then again this morning... same thing stuck in a boot loop.
As happy as I am about her being able to restore it on her own...it takes a while and shes at work by the time its done! and the maddening part is that I booted it multiple times the nite before in both cases...
What could be causing this? Things I haven't tried yet?
I checked the SD to make sure there weren't any update.zips or similar,
I have not formatted the SD, that I will do tonight.
I read the whole thread regarding Clockwork I didn't see anything I might have messed up...Does this have to do with uSD boot priority and maybe I have a hidden file on the SD?
And I have really searched for something similar, people have bootloops but not like mine that I can see.
Sorry for being long here but this is frustrating, I'm not all that new at this I've been voiding my warranties for a long time and this one has me stumped...
Thanks in advance for any reasons, suggestions.
EDIT: Looks like I am not alone, I am seeing more of these problems pop up now.

Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?

eyecrispy said:
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
Click to expand...
Click to collapse
I have disabled OTA but if this is a registration/ auth problem I guess it wouldn't help.
I have NOT gone the 1.0.0 then root path and that sounds like a good next step, thank you.

update for nook

B and n tried to send out an update over the air....anyone know what its about?
afraid it'll mess my rooted book up
I have the 1.0.1 update already and rooted it with nooter

Did you already have the 1.0.1 update installed?

Nothing new about an update on B&N forums or their nook color update page.

This is 1.5. Just getting ready to insert card into nook to root. Maybe I should wait.

I just got an update notice also. I already have 1.01 so not sure what the update was for. I said not now so I should get the notice again later. Hopefully it wasn't a fluke and its actually 2.2!!!!
Sent from my Nook Color using XDA App

I have 1.01 as well and received an update notice somewhere between 1'00 and 1:30 Central Time.

Yeah that was prob around the time I got mine. Was just about to start reading before I go to bed. Now i can't sleep cause I'm trying to figure out what kind of update it was!!
Sent from my Nook Color

Can the next person to get this PLEASE accept it...
It would be interesting to see what the update actually is

If i get it again ill accept it. Since nobody knows what it is I might as well. I just figured I would do some research and see if anybody else had already dl'ed it yet.
Sent from my Nook Color

I don't recall accepting an update, but something messed up my nook while I wasn't using it, and it fits the timeline of this update. I had to enter recovery and things seem to be working alright. I would advise that people make a recent backup just in case something similar happens to them. Definitely upset that I lost most of my recent changes.

Hey something defenently trying to get through I am getting a meesage of something is wrong in your nook and system restarts and wides data and cache...
No updates though.
I have reverted to stock 1.0.1 using the 8 failed boot sequence and waiting to see what comes through ...

I left a stock 1.01 NookColor on over night and I didn't see a new firmware push. But then I never got the 1.01 firmware either, I had to manually download and install it I didn't see anything on B&N's update site either. I'm curious to see what it is.

Update 1.5? Me thinks you own a NK ("Nook Klassic" for lack of better name)
tblack said:
This is 1.5. Just getting ready to insert card into nook to root. Maybe I should wait.
Click to expand...
Click to collapse
The only Nook with a v. 1.5 is Nook Klassic. As far as NC is concerned, I have also received several "update" notices for NC - the green "N" at the bottom left - even though I've already updated manually to 1.0.1 so I could AutoNooter 2.12.25. Ignore these messages. You're already up to date.
Later!

wpnyc2009 said:
The only Nook with a v. 1.5 is Nook Klassic. As far as NC is concerned, I have also received several "update" notices for NC - the green "N" at the bottom left - even though I've already updated manually to 1.0.1 so I could AutoNooter 2.12.25. Ignore these messages. You're already up to date.
Later!
Click to expand...
Click to collapse
I'm like gedster314, I left NC #2 on w/WiFi overnight w/charging and had WiFi on for 2-3d IIRC while using it and NEVER got an OTA update notice, so I also ended up manually upgrading it to 1.01.
I haven't noticed any update notices on mine, but I mostly have WiFi off to help extend batt runtime since the batt life isn't so hot... (or maybe I've just been spoiled by my gTab batt runtime w/WiFi running nearly constantly...)

Nook will turn on by it self after 5 minutes or so

First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)

Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.

To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.

I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.

Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.

lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.

Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state

I can't believe I'm the only one with this problem

lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.

I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue

woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?

Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.

oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.

woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?

I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.

unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.

Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.

Well, strange that only two or three of us noticed this strange problem.

Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...

I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.