Thread: Block OTA by removing ota related binaries
View Single Post
Old 03-23-2021, 01:24 PM   #39
j.p.s
Grand Sorcerer
j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.
 
Posts: 5,821
Karma: 104662271
Join Date: Apr 2011
Device: pb360
Quote:
Originally Posted by hius07 View Post
The question is why creating the update.bin.tmp.partial folder doesn't prevent creating temporary download file with the same name on newer firmwares? Can we protect this folder against forced deleting by the system? Maybe, creating some files inside it and chmod them?

I think the reason is in the posts by NiLuJe quoted below.


Quote:
Originally Posted by NiLuJe View Post
Note that the "Prevent OTA updates" button in the Helper extension does just that, so it may help.

It will NOT on 5.12, as this one appears to have taken the bull by the horns and decided to workaround the issue by forcefully removing the block folder and stop supporting SKIP_UPDATE_CHECK .
Quote:
Originally Posted by NiLuJe View Post
@hius07: https://www.mobileread.com/forums/sh...&postcount=477 & https://www.mobileread.com/forums/sh...1&postcount=80

@j.p.s: You don't even know how right you are ;D. It's indeed a hardcoded rm -rf system() call .

All of that is in one of the ota* *binaries*, I can't remember the exact one OTOH, probably otaupv3 or something.

You'll need a < 5.12 version to compare to, of course .
j.p.s is offline   Reply With Quote