yashsingh1/xdaforums huggingface dataset:
[Nook Color General] markiejones:
It could be a boot-up process, but I doubt that because I would imagine that stock users would rarely need to shutdown. It's definitely not a sleep process, because there is no wifi on stock nook at sleepytime. Probably a small piece of some random "Hey I'm a Nook Color" daemon or what have you.
[Nook Color General] bugeyed1:
Can someone please answer this? I am in pertty much the same situation. It would be nice to know exactly what happens if I am at auto-nootered 1.0.1 & get the 1.1 OTA update. What will I have & what are my choices other than wait for a 1.1 auto-nooter.

Thanks,

kev
[Nook Color General] volwrath:
You might be able to sideload the 1.0.1 update. Also I think that CWM might block the update, so the easiest solution to block the update is install CWM
[Nook Color General] eyecrispy:
I don't think OTA happens on boot because the first NC i had auto updated to 1.0.1 like a min after i put it to sleep after some light reading. I got no prompts or anything. I just did it. I am more likely to agree with the person who suggested that it updates during NC sleep. And I've been wondering why I haven't had any updates (i'm still on 1.0.0). It's likely because I have a sleep profile to turn off wifi when the NC is sleeping.
[Nook Color General] A. Nonymous:
This URL doesn't resolve for me either. I like the concept behind this update though as it would block all updates period. I wonder if you could just block barnesandnoble.com this way and block updates? Or does it use a different server name?
[Nook Color General] MACLUIS1:
Don't know if this has happened to any of you but I was trying to install the scremer kernel when it started to bootloop. I decided to restore with ClockMod and what I've got instead was the 1.1 update. I still have Seam an Superuser but the Market, RootExplorer, Mount Remount, and most of my applications, almost 200of them are gone. Help anybody.
[Nook Color General] khaytsus:
Had you modified the build.prop or not?
[Nook Color General] A. Nonymous:
Modified the build.prop. I got the message that I was updated. Does this block the update or is this a false positive? Inquiring minds want to know. News at 11.
[Nook Color General] Smoghog:
Mine worked as well. Replaced my own Build.prop with the modified one you uploaded, got the false update notification, everything's running smoothly. Thanks! :)
[Nook Color General] mattg_20:
Is there a way to get this done without using Root Explorer or ADB? I don't have either one installed. I tried using Astro but it won't let me paste the new build.prop file in the /system folder. Any suggestions?

Thanks,

Matt
[Nook Color General] bdcrim:
Might consider buying root explorer. It will come in handy in the future as the nook continues to develop. Maybe not what you wanted to hear, but you asked. Well worth the money. Good luck.
[Nook Color General] onerikeronebridge:
I just used root explorer to modify the build.prop file in /system and so far it seems to be working perfectly, updated with green nook icon in notification bar, etc. Don't know if you need it, but for those who are as much of beginners as I am, an instruction set is always helpful.

1. Inside root explorer, navigate to /system, press the "Mount R/W" button at the top of your screen;

2. Look for build.prop;

3. Long-press build.prop and select "open in text editor";

4. Now that you're in the text editor, modify the file according to http://xdaforums.com/showpost.php?p=10917382&postcount=64

5. Once your file looks identical to the 1.1 build.prop, press menu-->save and exit;

6. Exit root explorer and reboot!
[Nook Color General] callmeraymon:
Using ADB

adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
[Nook Color General] JF-WS6:
if you have root explorer do you really even need Astro? I have Asto now and just bought Root Explorer to try to attempt this OTA block because i couldnt figure out adb and got frustrated with it. Im a newbie
[Nook Color General] bonzer2u:
I would assume a false positive???

which is fine by me until the dust settles on a new 1.1 autonooter....
[Nook Color General] khaytsus:
Well, busybox has vi.... Muahahaahaha.
[Nook Color General] khaytsus:
We'll know if someone has done this, rebooted, sure he followed the instructions, BUT STILL GETS THE OTA. So nobody really knows ;)
[Nook Color General] bdcrim:
You really don't need astro. An easy solution is to download from the 1.1 link in the OP to your sd card. Move that file to the system directory and paste after changing to r/w. Move the build.prop in the system directory to the sd card in case you need it later and rename the newly inserted build.prop1.1 to read build.prop. Be sure to change permissions of new file to match the one you moved. Reboot and you should be good to go.
[Nook Color General] Tripb3:
Thanks

Will give this a try if Froyo on eMMC does not work for me.
[Nook Color General] bulletproof1013:
Works great thanks
[Nook Color General] pfcwintergreen:
Still no update push or notification, unless the one random restart I had was infact it.After this sudden reboot nothing changed, I wasn't informed of any update, I'm still on 1.01 and still rooted.

Guess either the build prop fix or the freezing of com.bn apps might be working?
[Nook Color General] markiejones:
That's my take as well - this "trick" does fool the operating environment into thinking it's been updated. But that doesn't mean it will fool whatever process triggers the OTA check. It might be looking elsewhere for the information that tells the process to trigger the download. And build.prop only tells the notifier service (hence our cool message).
[Nook Color General] Hest88:
Thanks for this. I also grabbed the file from your dropbox and replaced the old file via Root Explorer. I got the faux updated notice, so I'm keeping my fingers crossed that this will indeed block the automatic update.
[Nook Color General] bah!:
Or the update might not have gotten to you yet.

So far I haven't done anything to stop the update and haven't been hit with it either. Of course, I think I read that CWM would cause the update to fail, but I'm not sure if that's true or not.

I guess I'll find out in the coming days. :)
[Nook Color General] jwigginton:
Thanks. Did via root explorer, let's see if it works

Josh
[Nook Color General] oldtimercurt:
Thanks to onerikeronebridge for the neat little recipe. As an old man not used to messing with the innards of these electronic gadgets ;) I kept getting file was read only when tried to go to the text editor. Silly me, I hadn't noticed that the white box was what you would toggle to not where you were. Once I figured that out it was pretty simple. My fat fingers made getting the cursor in the middle of a line difficult so I had to retype more than I wanted to. Anyhow, got the "faux green n" on reboot so hopefully I'm protected for the time being.

OTC
[Nook Color General] Hest88:
Small strangeness. Three times now, the book I've been reading (a B&N one using the stock reader) had flickered back to my home screen and flickered back. Plus, when it went to sleep once the lock screen was there even though I've been using "no lock." I just rebooted again and am hoping whatever bugginess caused that will go away, and it's not some lasting weirdness that happened during the faux build.prop process.

ETA: Okay, no dice. Just took it out of sleep again and the lock screen returned. When I slide the lock it went back to my book, then flashed back to my homescreen for a split second, and then went back to my book. Hm.
[Nook Color General] kenrothman:
help!!!

So, i used the build prop file from the dropbox link.

used root explorer to copy it to /system like the instructions said.

now when it boots... i get a blank screen!

did i brick it?

what can i do here?

i'm a nook noob.

help me!
[Nook Color General] Hest88:
Oh, and now it looks like my Ultra Keyboard was somehow uninstalled. Curiouser and curiouser.
[Nook Color General] slugbug2010:
I am still confused. Please pardon my newbness here, I'm an old pro on my evo, but thus is quite different. Fun being part of the beginning though :-)

I renamed the otacert file, but now we know that doesn't work? So I need to ....... copy and paste this fix via root explorer, no adb or SD card needed right?

I am reading every day and trying to keep up, but don't grasp all the different terms yet. Thanks

traced using ultra keyboard
[Nook Color General] kenrothman:
forget it. fried it and gonna start over. :(
[Nook Color General] khaytsus:
When the (real) 1.1.0 update hits, it'll format /system. So if your keyboard is missing, I suspect you're on 1.1.0. Just a guess here. Have you actually looked in /system/apps to see if it's missing and just isn't working for some reason?
[Nook Color General] Hest88:
The apk was still there, but I had to reinstall it. Hm. This morning my lock screen was on again and that flash happened again. So you're speculating that I somehow got updated to the real 1.1.0 which has caused all of this?

WiFi has been mainly off. I even used a USB to move over your dropbox file. ;) However, I guess it's possible it snuck through. I'm wondering if I should change the board file back and try again.
[Nook Color General] khaytsus:
If the APK is still there, then absolutely no you did not get the 1.1.0 update, it formats /system
[Nook Color General] Ncminn:
overload of info...

I have been following the threads since the upadate was announced. I have had my wi-fi off for a couple days now trying to sort this out. I am on 1.0.1, autonooter 2.12.25....nothing else. I dont have CW recovery installed. Just the basic nooter stuff and about a dozen apps and Zeam. Can I let 1.1 install and still use the apps I have? I know the market will not work on 1.1, but will my gmail, dolphin browser, nesoid work, ect... work?

I prefer to keep it as simple as possible without messing with system files and other things I have no knowledge of. It has been tough keeping up with all the ideas and solutions.

BTW...why do tablet and phone users accept that updates are automatically pushed on them without a choice. This would never happen on your PC or Mac. You always have the option to install or decline updates. Maybe I am missing somthing, but it would be nice to just say "no thanks", dont need your updates right now....
[Nook Color General] Hest88:
Okay, thanks. I'm flummoxed about the weird hiccups. All I did was rename/replace the file. I don't have CW Recovery; I don't have Titanium Backup. I don't have a Task Killer running. Yet right after I installed the faux build prop file these little demons popped up.
[Nook Color General] MissKristine:
I'm a beginner, too, and I have never used root explorer before today. When I navigate to /system and tap the Mount R/W button at the top, nothing happens. I've tried to refresh, exit out and reboot, nothing will get it to change from read only. Any ideas what I'm doing wrong?
[Nook Color General] dmurray14:
I did the autonooter on 1.0.1. Also edited the build.prop to stop the 1.1 update. Mine just rebooted and said I was updated to 1.1.

All my stuff still works, including the Market. Was I really updated?
[Nook Color General] A. Nonymous:
Do you still have root?
[Nook Color General] sweetros:
About 36 hours later, after doing this method, and still haven't had the OTA pushed to my device (was on wi-fi the whole time). Hard to _confirm_ it as a successful method, but I can say that (so far) it's not a failed method.

FYI - I did both of the following: renamed "otacerts.zip" and modified "build.prop" (per the instructions using Root Explorer).

My only recommendation to your listing is to boldface "reboot" in the instructions. I missed it the first readthrough and just did it to see if I "updated" without updating. Once I rebooted it shows that it has updated to 1.1 (even though I know it really hasn't - heh heh).

Thanks!
[Nook Color General] 66cat389:
Thank you for this, I currently have my nook color rooted, running an OC kernel and pretty much have it running exactly the way I want. If I can avoid the headache of having the 1.1 update jammed down my throat, the it's all the better.

Besides, I can live without pinch to zoom. Which as far as I can tell is really the only noteworthy addition to the 1.1 update. There are much worse things in life to be without.

So Thank you again. Worked like a charm.
[Nook Color General] bonzer2u:
Permenant BN-OTA block database hack available

Greetings,

No need to keep editing your build.prop file and hope you can before the next BN-OTA push....

Here is a one-shot end to all future BN strong-armed updates:

http://xdaforums.com/showthread.php?t=933291
[Nook Color General] gab1972:
This may be an extremely dumb question, but I have always just used adb commands from the device using Better Terminal Emulator. So, I tried using it on the rooted Nook and I'm getting bash: command not found - or something similar to that. It's like BTE isn't recognizing adb commands. Anyone?
[Nook Color General] khaytsus:
So has anyone gotten an OTA since pushing the build.prop (and not tweaking other things, sqlite files etc)? No OTAs here on my two NC's.
[Nook Color General] khaytsus:
Still no OTA. :cool:
[Nook Color General] wrenchneck:
so a quick run down of what I have done:

1. edited the devicemanager.db (first attempt) for manual

result: still received OTA

2. in unit edit of the build.prop

result: still received OTA

3. ADB pull/push build.prop with on pc edits done

result: still received OTA

The 2nd attempt did not notify me that the update had occurred so I took that as it had not taken. However when I used the ADB method, I still had a rooted NC with a green N telling me I was now updated. Checked system info and the build version was 1.1 as well. Thought all was well, about 15 minutes later went to use the NC, received the OTA YET AGAIN.

Does anyone actually have a fix for this that has worked for more than say 15 minutes? I have run out of methods to block this OTA now from what I am seeing and still everyone is just hoping their method works.

So I will restore once again to a back up and turn off wifi...
[Nook Color General] khaytsus:
You sure that you updated the build prop, MADE SURE THERE WAS NO UPDATE WAITING in /media, then rebooted to make the build.prop active?

Nobody else I've heard of this method failed.
[Nook Color General] wrenchneck:
Howdy, just an update and a question. I had edited the build.prop, rebooted the unit and all has been fine since last week. However I went to go into the B&N store today and have suffered the FOTA again. I was wondering if anyone else has had this happen to them? Oh btw, my nook has been on the wifi the entire time and I have been using it so it seems that something hasn't been accounted for when accessing the store.

ANy ideas?

***NM it appears to be an authorization issue that is restoring my unit. I will have to deal with that.***
[Nook Color General] khaytsus:
Yeah, I don't think anyone has ever figured out what makes SOME people get a full reset from the B&N Store app and others don't (like me and my wife).

BTW she buys and loans books all the time, and we've both been into B&N with our NC's since nooting them. Both on 1.0.1, no problems. No free in-store reading, but that's not a big deal.
[Nook Color General] wrenchneck:
I was good until I tried to access the store, My unit isn't registered anymore evidently and now it says I have to reset my unit in order to re-auth/re-register it. Since I didn't actually purchase the NC as an e-reader it isn't terribly important, all I wanted to see was if there was a cheap Wired subscription!
[Nook Color General] khaytsus:
Sorry this was an issue for you, but again, happens to some people and not quite sure why. Unrelated to the OTA change of course, just something to do with rooting it and authentication.

Mine and my wifes still are able to go to the physical store and use their wifi, read books, purchase books, loan books, etc..
[Nook Color General] khaytsus:
Anyone willing to try a new build.prop-1.2.0 to see if it avoids the OTA?

I've replaced the ro.build info from the new 1.2.0 into the 1.1.0 build prop I created before..

THIS COULD EAT BABIES. Don't do this if you're not willing to have boot loops in case this is wrong. But if you are please let me know if it works and boots. If so, hopefully this will keep 1.0.1/1.1.0 folks from auto updating until 1.2.0 is Auto Nooted.

PM me for the link.
[Nook Color General] khaytsus:
1.2.0 build.prop is in the first post, two folks have tried it and said they got the expected green N "1.2 update" without any actual update. Time will tell if it blocks the OTA but it did for 1.1.0 so I expect it will for 1.2.0.

Per a suggestion from a user, I'm not using the fingerprint from 1.2.0, rather one from Sholes. And the full market, including some often missing apps seems to be there.

If you try it, let me know how it goes! Thanks!
[Nook Color General] doncaruana:
Still offline, but was doing a side-by-side in the build.prop from 1.1 and 1.2. Interesting that they finally updated the product/manufacturer from LogicPD Zoom2 to BarnesAndNoble NOOKcolor
[Nook Color General] doncaruana:
Kind of a dumb question, I suppose, but this should be okay to put on a 1.01 rooted as well, right? I mean the point is simply to trick the updates, so id doesn't matter what's actually on the nook itself...right?
[Nook Color General] khaytsus:
Sorry if that's not clear, yes, the "1.2.0" is to pretend you're that version. The actual version being 1.0.1 or 1.1.0.
[Nook Color General] doncaruana:
Not you - it's me. Being overly paranoid. Dropped it on my 1.0.1 and restarted, got the green n and the notice that says I've updated to 1.2. Still too chicken to go on wireless, although I should - have full Rom Manager/CMR backup along with TiBu for several apps.

Next is 1.1, now that I (quite mysteriously) *finally* got adb working over usb on it.
[Nook Color General] noaxis2:
Okay...I tried this on my rooted 1.1...caught in reboot loop. "Touch the future of reading" followed by "Loading..." then blank screen.

The only thing I can think of is the file was corrupted (I renamed it to build.prop using Root Explorer) and/or I didn't mount or unmount (whichever I was supposed to do) before moving or pasting the new file.

Any ideas? I've gone back to 1.01...might get up to 1.1 tonight...if I root again, I'll want to block the updates so I'll have to try this again. Might have to try the CM7 SD card thing.

Thanks!
[Nook Color General] khaytsus:
Not sure, but you could not have copied it to /system without remounting. I've always used adb, but should be all the same.

Did you edit the file or anything? Maybe you edited it in some dumb editor that adds linefeeds, etc..
[Nook Color General] noaxis2:
All I did was download the file to my computer, renamed it to "build.prop", copied the file to the nook via USB, moved it to the /system using Root Explorer. I never attempted to open the file.

Thanks for any insights!
[Nook Color General] giedrys:
So does it work 100% on rooted 1.1 to prevent OTA 1.2 update? Yes or no?
[Nook Color General] doncaruana:
There has only been one report of it not working. To be safe, I did all 3 "tricks" and have not received the update. If you need to find the other two, check out here.
[Nook Color General] giedrys:
Well I tried to use this method via Root Explorer and messed thing up. Now my rooted 1.1 NC wont boot past nook logo and black screen. I did backed up original build.prop file to SD card. How to go back and fix that?
[Nook Color General] khaytsus:
Responded in PM and suggest to get on IRC for steps... Either use ADB from a clockworkmod SD boot and copy the backed-up build.prop or something like CM7 on SD card and the terminal app to copy the original build.prop back in place.

I've edited the first post to say NOT to use Root Explorer. I dunno what it's doing but it's messing up something...
[Nook Color General] giedrys:
Thanks, I'll try. I guess Root Explorer is not the way to go here.
[Nook Color General] khaytsus:
Updated to 1.3.0, let me know how it goes folks. I have gone ahead and made two build.prop's, one if you're still on Eclair and one if you're on Froyo. Not sure if it matters, but there's a few things like SDK version that I felt maybe needed separating.

DO NOT USE ROOT EXPLORER TO DO IT. You are warned. Several people have had bloops doing this, but doing it over ADB works fine. Why? No idea.
[Nook Color General] insink71:
Thanks

While waiting for my sd card reader/writer to arrive from Amazon, I will just have to bite my fingernails and hope I don't get updated. Just wondering is there any way to prevent the update on a non-rooted device? Like can I do a factory reset (power button and n) while its trying to install the update or some way to turn the unit off then boot from sd when I get it made. I won't venture into 1.3 without a known, documented root process. Thanks in advance for any suggestions.

Edit: Call me superparanoid, but I disabled wifi and turned the nook off. I'll struggle along with my smaller-screen G2 until I get what I need. Thanks again.
[Nook Color General] dtbrewer:
I think this link gives an easier to follow method for the sqlite editing version of the update block. It worked for me for 2 months after the 1.1 to 1.2 update came out.

http://xdaforums.com/showthread.php?t=946969
[Nook Color General] w8wca:
I think it was HamNCheese that posted this before on another forum - and I have used it and not had any OTA updates.

Just modify /etc/hosts - add this line:

127.0.0.1 images.barnesandnoble.com barnesandnoble.com
[Nook Color General] jpeg42:
Just curious wouldn't that block anything from B&N? Then you couldn't get books, newspapers, etc?
[Nook Color General] w8wca:
It has not stopped me from getting ebooks.

(I do leave the existing line in "127.0.0.1 localhost " and add this below it fwiiw)
[Nook Color General] tjupille:
But it *does* prevent book cover images from showing when you shop.
[Nook Color General] tjupille:
FWIW:

I just loaded the 1.3 build.prop using Root Explorer. No problems. Got green n on reboot and system thinks it's 1.3. I restored the original hosts file and book covers now show in shop.
[Nook Color General] squall_x:
So far this has worked for me to prevent from 1.01 to 1.2 and from 1.2 to 1.3
[Nook Color General] fpga_guy:
The sqlite method of change fota from "auto" to "manual" had worked on a NC with BN 1.1 since April. This has the advantage of not changing build prop each time a new update comes out.
[Nook Color General] w8wca:
Thanks for that info.

I never shop on my NC except for Android Market, but it is good to know.
[Nook Color General] twhite6878:
Huh?

I am a n00b, obviously. I went the Root Explorer method for modifying the build.prop. Boot looped. Then I tried to adb but it kept saying it could not find the build.prop file. Where do I put the build.prop file so that the adb command can find it? I've tried the SQLite registry modifier. I still got the 1.3.0 update. I am about to just say screw it and keep it as an e-reader. I manual nootered it using mn 4.6.16. I really want the damn thing rooted and to stay that way without the B&N strong arm.
[Nook Color General] khaytsus:
Which part of the original post are you not getting? I said clearly, in bold red, not to use Root Explorer.

As for the rest, you must be typing something in wrong.
[Nook Color General] twhite6878:
I've downloaded the build.prop file but I do not know what directory to put it in, as adb is not finding the build.prop file.
[Nook Color General] joej:
the build.prop file is in /system . you will need to change the volume to RW to update it.
[Nook Color General] khaytsus:
Download it wherever, and adb push from that directory to /system, just like is in the first post. adb doesn't "find" the build.prop file, you tell it what the file is.

I suggest just copying the build.prop-1.3.0-froyo or whatever to your SDK Tools folder where adb is, then just adb push build.prop-1.3.0-froyo /system/build.prop
[Nook Color General] twhite6878:
I did this over and over and adb cannot CANNOT find the build prop file. I am getting frustrated. Yes, I wrote it EXACTLY as it is written on page 1. I put in the proper directory. It is not working. It says, "adb: not found".