Block BN OTA Updates the EASY way!!!

Search This thread
By:
Advanced…
R

RootNewbie

Member
Jan 20, 2011
14
7
First, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development... Link to post.

Having played with adb for hours and not being able to get sqlite working in cmd. I tried browsing to the file the script in the above post appeared to be editing with Root Explorer. To my surprise, when you click on the devicemanager.db file, Root Explorer gives you an option to buy SQLite Editor. Which I did.

Required Apps:
- Root Explorer (in market)
- SQLite Editor (in market)

Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"

Assuming this is what the scripts are doing, your nook color should now be blocking BN OTA updates. The best part is that you can do all of this from your nook color. :) Hope this helps!
 
  • Like
Reactions: swedenboy, raye1010, Droiddict and 2 others
R

RootNewbie

Member
Jan 20, 2011
14
7
khaytsus said:
Really? Or push a modified build.prop, done... *shrug*
Click to expand...
Click to collapse

Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
 
  • Like
Reactions: MattZTexasu
K

khaytsus

Senior Member
Apr 8, 2008
7,258
1,175
Central Kentucky
RootNewbie said:
Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
Click to expand...
Click to collapse

Nobody I'm aware of, including my two NC's. Perhaps you're confusing updating the build.prop with renaming the otacerts file?

http://xdaforums.com/showthread.php?t=930382
 
J

JF-WS6

Member
Jan 25, 2011
39
1
RootNewbie said:
First, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development... Link to post.

Having played with adb for hours and not being able to get sqlite working in cmd. I tried browsing to the file the script in the above post appeared to be editing with Root Explorer. To my surprise, when you click on the devicemanager.db file, Root Explorer gives you an option to buy SQLite Editor. Which I did.

Required Apps:
- Root Explorer (in market)
- SQLite Editor (in market)

Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"

Assuming this is what the scripts are doing, your nook color should now be blocking BN OTA updates. The best part is that you can do all of this from your nook color. :) Hope this helps!
Click to expand...
Click to collapse

Thanks for posting this. I'm sure it will help someone out. It would have been me a week or two ago. I was trying to figure out how to change this value to avoid the OTA and really didnt understand ADB, SDK, Sqlite or any of that then. when i first opened Root explorer i remember it asking me if i would like to purchase it and i declined, now if i only would have known how easy it could have been.
 
R

redking79

Member
Oct 12, 2008
19
2
RootNewbie said:
Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
Click to expand...
Click to collapse

I agree. Changing the setting in devicemanager.db is A LOT cleaner than the build.prop fix.
 
L

Leumas63

New member
Feb 15, 2011
2
0
Slightly off-topic: I made this change (in devicemanager.db) to disable B&N updates. Whilst in the database, I noticed a table called Tasks that has 5 entries with types 100, 101, 102, 3, 2. The types 100 & 2 are tagged as enabled, the others are disabled. They have a date_next_run column. I imagine this is some kind of scheduling. I haven't worked out the date format. Does anyone know what these tasks will do - I would imagine one of them forces a B&N update?
 
Last edited:
C

crispian

Member
Jul 7, 2007
16
1
RootNewbie said:
Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"
Click to expand...
Click to collapse

Thank you for this- It's nice to find a nice, easy, self-contained way to ensure my NC will stay the way I have set it up 'til I decide otherwise.

One question though- to make it stick shouldn't there be one more step-
10. Reboot?
 
D

DBS_FamilyDoc

New member
Dec 26, 2010
1
0
Block OTA updates

Xboxexpert has posted a bat file for download in a zip file Block updates.zip. Has anyone used this?

I need instructions regarding running the bat file.

Do I load the contents of the zip file on my SD card or do I open a command prompt box?

What do I do to run this bat file?

Thank you.
 
S

sonatacreative

Member
Dec 2, 2010
8
0
Wow this is an awesome find. Can anyone verify that this did indeed work for them? I have my rooted NC running 1.1 smoothly with all apps running perfectly. My final task is to stop OTA's from triggering. I don't feel confident doing this via ADB but using this method on the NC seems easy. Does this sound the same thing as the bat file does from the other thread? Thank you all for your amazing help!
 
W

wrenchneck

Member
Mar 7, 2011
18
0
I have been through this 4 times so far and have been unable to get it to stick. I have backed up the rom after installing sqllite and root explorer, modded the registry, rebooted and still getting the damn OTA. Anyone else having this issue or has figured out if there is another entry that needs to be edited to defeat this?
 
W

wrenchneck

Member
Mar 7, 2011
18
0
Nm, I edited the url that the fota uses to check for updates so it is "dead"
backedup the rom again and have yet to see fota from BN. *fingers crossed as this is annoying*

****NM this didnt work either****
 
Last edited:
W

wrenchneck

Member
Mar 7, 2011
18
0
Thanks khaytsus! I do believe that has done the trick. I went ahead and edited the build.prop versus pushing it but we will see how it fairs now that i have hit wifi back on
 
G

giedrys

Senior Member
Mar 12, 2006
56
1
Does this method still works to prevent 1.2 ota update? it surely looks the easiest method of all.

Yes or no?
 
You must log in or register to reply here.

Similar threads

eyeballer
[GUIDE] Install CM7 or CM10 + Recovery to EMMC - ALL NOOK COLORS! (Updated:11/19/12)
Replies
878
Views
511K
LKJEFoi234
LKJEFoi234
nootered
[HOW-TO] : Restore Nook Color back to stock EASILY!
Replies
190
Views
185K
leapinlar
leapinlar
D
  • Poll
With new update pending, what is best way to block OTA updates?
Replies
45
Views
13K
D
dalex7777
K
Want to try to avoid 1.3.0 OTA? Modify build prop?
Replies
122
Views
34K
K
khaytsus
D
The status of Android 3.1 Honeycomb on the Nook Color
Replies
160
Views
139K
L
luigi90210

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 5
    R
    RootNewbie
    First, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development... Link to post.

    Having played with adb for hours and not being able to get sqlite working in cmd. I tried browsing to the file the script in the above post appeared to be editing with Root Explorer. To my surprise, when you click on the devicemanager.db file, Root Explorer gives you an option to buy SQLite Editor. Which I did.

    Required Apps:
    - Root Explorer (in market)
    - SQLite Editor (in market)

    Process:
    1. Open Root Explorer
    2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
    3. Select "registry" - this should open up a spreadsheet looking file
    4. Find row: com.bn.device.fota.mode
    5. Drag over to the column labeled "value"
    6. Press and hold "auto" until the "Actions" window pops up
    7. Select "Edit Field"
    8. Replace auto with manual
    9. Select "Save"

    Assuming this is what the scripts are doing, your nook color should now be blocking BN OTA updates. The best part is that you can do all of this from your nook color. :) Hope this helps!
    View
    1
    R
    RootNewbie
    khaytsus said:
    Really? Or push a modified build.prop, done... *shrug*
    Click to expand...
    Click to collapse

    Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
    View

New posts