MobileRead Forums - View Single Post - Block OTA by removing ota related binaries

Hzj_jie · 03-06-2020, 03:08 PM

This is still in the evaluating stage; I will update the post to explain whether it would permanently work or not.

My use scenario is pretty common, I need wifi to sync reading progress between my devices through koreader, use wikipedia, etc. So I cannot disable wifi just for blocking ota.
But ota breaks jailbreak easily, especially 5.12.*. So yesterday, my voyage automatically updated itself; and I have to run emergency again to bring back my jailbreak.

The idea is also very straightforward. I randomly found there were two processes on kindle otaupd and otav3. The first one looks like a daemon, the second one looks like the real implementation of ota. So I renamed these two files in /usr/bin/ to otaupd.bck and otav3.bck and manually kill the existing processes. After that, the processes definitely won't be brought back again.
So far, no obvious negative impacts were found.

I have done the same thing on both a voyage and a pw4. The voyage has updated to 5.12.4, and the pw4 is kept in 5.12.3 until now.
I will let you know if it can permanently block ota.

03-06-2020, 03:08 PM	#1
Hzj_jie Member Posts: 21 Karma: 638 Join Date: Feb 2016 Device: kobo aura hd	Block OTA by removing ota related binaries This is still in the evaluating stage; I will update the post to explain whether it would permanently work or not. My use scenario is pretty common, I need wifi to sync reading progress between my devices through koreader, use wikipedia, etc. So I cannot disable wifi just for blocking ota. But ota breaks jailbreak easily, especially 5.12.*. So yesterday, my voyage automatically updated itself; and I have to run emergency again to bring back my jailbreak. The idea is also very straightforward. I randomly found there were two processes on kindle otaupd and otav3. The first one looks like a daemon, the second one looks like the real implementation of ota. So I renamed these two files in /usr/bin/ to otaupd.bck and otav3.bck and manually kill the existing processes. After that, the processes definitely won't be brought back again. So far, no obvious negative impacts were found. I have done the same thing on both a voyage and a pw4. The voyage has updated to 5.12.4, and the pw4 is kept in 5.12.3 until now. I will let you know if it can permanently block ota.