View Single Post
Old 06-14-2018, 03:48 PM   #3149
DuckieTigger
Wizard
DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.
 
DuckieTigger's Avatar
 
Posts: 4,763
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
Quote:
Originally Posted by bz9993 View Post
Thanks! What is the most reliable way to block OTA upgrades for now while I consider this, so that I can take the unit online so that I don't have to sideload everything (assuming there *is* a reliable way to go online and block OTAs!) Is there any downside to registering the unit in this context? Thanks again!
There is no downside concerning ability to jailbreak (other than conspiracy worries) from registering.

To block OTA updates, just follow the instructions in the provided link for you in other post:

Quote:
Originally Posted by ilovejedd View Post
a) https://wiki.mobileread.com/wiki/5_x_Jailbreak (I used 'update_pw3_factory_5.8.9.0.1.bin', link for multi-part zip in wiki)
TLDR, specifically this part from it:

Quote:
Currently the best way to avoid OTA updates is to add the OTA blocker directory (folder) name to the top level of visible USB storage.
The blocker directory is named: update.bin.tmp.partial
Use that exact name, no additional extension, no contents.
DuckieTigger is offline   Reply With Quote