Thread: OTA blocking
View Single Post
Old 01-16-2018, 01:33 PM   #2
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 910
Karma: 3000002
Join Date: Jun 2010
Device: K3W, PW4
Quote:
Originally Posted by knc1 View Post
It looks like firmware 5.9.2 (and maybe earlier) can defeat our current means (a directory name) of blocking over-the-air updates.

As a temporary measure, keep the devices in 'airplane mode' to avoid updates.
This is specially critical for devices NOT YET running a firmware from the 5.9.x firmware series.
At least if you want to jail break the device, since we can not jail break any of the 5.9.x series firmwares.

If you want to know when a new blocking method is invented, just subscribe to this thread.
(And please, everybody else avoid posting a lot of 'noise' in this thread.)
Do you know how far this goes yet? In order to maximize my protection I not only created the top level directory, I created a sub-directory with a file in it and marked them all read-only. I have not tested this to see if it is sufficient, but perhaps someone with serial access for a fallback can test and see if this would be enough. Obviously they want to have serial access before the test to permit them to return to an earlier firmware release.

Dave
dhdurgee is offline   Reply With Quote