HTC M9 S-OFF In Less Than 24 Hours – No ETA On Release

HTC devices are no stranger to XDA’s Senior Recognized Developers … more

April Fools Round Up: The Year of Nostalgia

April Fools Day is once again upon us and as usual, tech companies everywhere have not … more

Android 5.1 OTA for Nexus Round-Up

The beginning of April is dominated by April Fools. There are jokes and pranks everywhere, which are … more

Official Lollipop for LG G2 Captured

LG is rolling out the Lollipop update for the LG G2. KDZ images for both 16 GB and 32 GB variants … 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
 
14 posts
Join Date:Joined: Jan 2011
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,152
 
7,101 posts
Join Date:Joined: Apr 2008
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
 
68 posts
Join Date:Joined: Mar 2008
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
 
14 posts
Join Date:Joined: Jan 2011
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,152
 
7,101 posts
Join Date:Joined: Apr 2008
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
 
39 posts
Join Date:Joined: Jan 2011
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
 
19 posts
Join Date:Joined: Oct 2008
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
 
302 posts
Join Date:Joined: Jan 2008
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,152
 
7,101 posts
Join Date:Joined: Apr 2008
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
 
2 posts
Join Date:Joined: Feb 2011
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