Tools BinaryRenamer - Block OTA Updates & Device Logging

[captdog]

I've just used this on my 15.15.1.1 & 5.16.2.1.1 paperwhites & all seemed to go well.

[b00kwyrm]

Originally Posted by Daviteusz

BinaryRenamer
Block OTA Updates and Device Logging

Installation:
—————————————
1. Copy the BinaryRenamer folder to /mnt/us/extensions
2. Run KUAL and block or restore things.

—————————————

Although this references installing in /mnt/us/extensions presumably by ssh, wanted to make sure that this corresponds to the extensions folder on the Kindle when mounting as removable drive AND that simply dragging and dropping into that folder will work (no permissions chmod that needs to be run on the file).

[j.p.s]

Yes, /mnt/us is what is exported over USB mass storage.

[Daviteusz]

Originally Posted by b00kwyrm

Although this references installing in /mnt/us/extensions presumably by ssh, wanted to make sure that this corresponds to the extensions folder on the Kindle when mounting as removable drive AND that simply dragging and dropping into that folder will work (no permissions chmod that needs to be run on the file).

I'm sorry for unclear instruction. I've updated steps for users that doesn't use SSH.
Should be okay now

[hondabf]

Greetings, thank you so much for this plugin.

Just installed this on my PW 4 running 5.10.0.2, is there a definite way to check the Kindle won't update? I haven't connected to Wi-Fi but wanted to make sure before enabling it.

I also wanted to ask if having Helper+ installed previously could affect this extension. Just before installing BinaryRemover, I re-enabled back the "PREVENT OTA UPDATE" option and removed the "update.bin.tmp.partial" folder as indicated. I also never installed renametobin beforehand.

[j.p.s]

It's iffy whether the update.bin.tmp.partial works beyond 5.9.x

Starting around 5.10.x the firmware has code to forcibly delete it but it is not known when it actually got enabled.

So far there have been no credible reports of renameotabin failing. It always turns out that someone didn't actually run it after installing.

[hondabf]

Originally Posted by j.p.s

It's iffy whether the update.bin.tmp.partial works beyond 5.9.x

Starting around 5.10.x the firmware has code to forcibly delete it but it is not known when it actually got enabled.

So far there have been no credible reports of renameotabin failing. It always turns out that someone didn't actually run it after installing.

Oh so that means my Kindle might be safer than before haha, that's good news!

[remember]

Thank you for this. I've always wanted a log disabler.

Do you know if the empty log files are still sent to Amazon, or does this somehow prevent them from being sent?

[ForumUser]

Originally Posted by remember

Thank you for this. I've always wanted a log disabler.

Do you know if the empty log files are still sent to Amazon, or does this somehow prevent them from being sent?

Is it still working? Could you please tell me your firmware version?