FORUMS

Xposed 3.0 Alpha 3 Released

A new alpha for the Xposed framework is out and brings several bug fixes. You’ll only need to flash … more

XDA Recap: This Week In Android (Apr 18 – 25)

Here in the digital XDA newsroom, we spend our days pouring over an average of … more

Sunday Debate: Custom ROMs vs. Modular Tweaks

Join us in a fun Sunday Debate on Mods and ROMs. Come with your opinions and feel free to … more

AOSP 5.1 Lollipop for Nexus Q

Google Nexus Q is an intriguing device released with Android 4.0 Ice Cream Sandwich. It was abandoned by … more
Post Reply Subscribe to Thread Email Thread

Block BN OTA Updates the EASY way!!!

8th February 2011, 11:07 PM |#1  
OP Junior Member
Thanks Meter: 7
 
More
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!
The Following 5 Users Say Thank You to RootNewbie For This Useful Post: [ View ]
 
 
8th February 2011, 11:36 PM |#2  
Senior Member
Flag Central Kentucky
Thanks Meter: 1,154
 
More
Quote:
Originally Posted by 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...

Really? Or push a modified build.prop, done... *shrug*
9th February 2011, 12:00 AM |#3  
V.A.T.Juice's Avatar
Member
Flag Pittsburgh
Thanks Meter: 7
 
More
Thats actually a good find because for a minute we were all sweating losing root over the 1.1.0 update.
9th February 2011, 12:30 AM |#4  
OP Junior Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by khaytsus

Really? Or push a modified build.prop, done... *shrug*

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.
The Following User Says Thank You to RootNewbie For This Useful Post: [ View ]
9th February 2011, 03:04 AM |#5  
Senior Member
Flag Central Kentucky
Thanks Meter: 1,154
 
More
Quote:
Originally Posted by RootNewbie

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.

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

http://forum.xda-developers.com/showthread.php?t=930382
10th February 2011, 08:01 PM |#6  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by 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!

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.
10th February 2011, 10:02 PM |#7  
Junior Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by RootNewbie

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.

I agree. Changing the setting in devicemanager.db is A LOT cleaner than the build.prop fix.
10th February 2011, 10:04 PM |#8  
Senior Member
Thanks Meter: 10
 
More
I just use a task killer and kill the B&N stuff... No updates here..
10th February 2011, 10:45 PM |#9  
Senior Member
Flag Central Kentucky
Thanks Meter: 1,154
 
More
Quote:
Originally Posted by redking79

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

Considering this is how all Android OTAs are determined.... eh, whatever floats your boat
18th February 2011, 05:59 PM |#10  
Junior Member
Thanks Meter: 0
 
More
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 by Leumas63; 18th February 2011 at 06:09 PM. Reason: clarity
Post Reply Subscribe to Thread

Tags
block ota updates
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes