Tools BinaryRenamer - Block OTA Updates & Device Logging

[nar001]

Hey so question, it seems that my Scribe had an issue when I used this, I did try to revert renameotabin to use BinaryRenamer, but it seems that it's now stuck on this? I'm not sure what to do to fix it (I still have access to it with USB, I just can't do anything on the display itself)

[juliazero]

It seems that after restoring renameotabin your kindle was start downloading update...

The problem probably wouldn't be there after disabling WiFi.

Try this:
• Remove the update.bin.tmp.partial file (if it exists) from the Kindle root directory.

[nar001]

Originally Posted by Daviteusz

It seems that after restoring renameotabin your kindle was start downloading update...

The problem probably wouldn't be there after disabling WiFi.

Try this:
• Remove the update.bin.tmp.partial file (if it exists) from the Kindle root directory.

It didn't, but I put the same firmware I was on in the root, and it was enough to unbrick it apparently, so that worked out! Tho now I'm stuck on the "Set up your Kindle" screen, which obviously isn't really useful (Tho it already was happening before, it's not your tweak's fault)

[juliazero]

Good thing it's not BinaryRenamer's fault, I hope you solve the new problem quickly.

[nar001]

Originally Posted by Daviteusz

Good thing it's not BinaryRenamer's fault, I hope you solve the new problem quickly.

Actually, not sure if you have any experience with it? I thought you were supposed to skip the Amazon set up screen, but there's no cross, or back, or skip button, only wifi setup and then logging screen, it's hard to find info on it

[juliazero]

Originally Posted by nar001

I thought you were supposed to skip the Amazon set up screen

I think this "feature" is only available in Scribe. When I configured Oasis 3, I was not forced to log in.

[nar001]

Originally Posted by Daviteusz

I think this "feature" is only available in Scribe. When I configured Oasis 3, I was not forced to log in.

Very weird

funny enough, the screen I attached a picture of happened again, and using the trick of putting the firmware file on it didn't work, but when I rebooted it went away. This time I'm sure I didn't have any firmware downloaded, as it was in airplane mode, I can check with a terminal emulator, but where are the firmware files stored? Or in-progress ones?

[tinbilly]

Confirmed working on KOA 1 & 2. Many thanks for your work!

[qqqqqqqqqqqz]

Originally Posted by mergen3107

Amazon logs and sends to servers EVERYTHING you do on a Kindle, even every single tap and time in milliseconds precision.

This script prevents all of that.

You can request your data from Amazon, you will get surprised.

How would I go about requesting that?

[mergen3107]

Just google “Amazon request data”?

[bookwormbuzz]

So I successfuly installed the extension on my jailbroken Paperwhite 1 (EY21). I went into Kual to disable Device Logging through BinaryRenamer. A moment after that, my device went into the launch screen with boy leaning on tree and it hasn't changed since yesterday. I've tried holding the power button for 50 seconds but it just flashes back into the same screen.

My Macbook recognizes the device when plugged in and it appears as “Amazon kindle” in the USB Device Tree when I’ve opened System Information, but it does not recognize it as a disk in Finder or Disk Utility. It does not appear as a disk in either places.

I've tried to use Terminal to find its disk identifier to try to mount it, but I cannot find it. Is the device bricked now?

[juliazero]

Another user experienced the same problem in #34.

If you have soldering skills, you can try this method to unbrick your Paperwhite:
https://gist.github.com/ramast/58633...2ecc96965d48ed

I’m not aware of any other methods at the moment.

I added a warning about this issue in the description under the "Block Device Logging" section several months ago. Sorry for not placing this warning in a more prominent location.

[juliazero]

BinaryRenamer v2.0 was released!

Changes:
- Fixed fbink location (now uses /mnt/us/extensions/MRInstaller/bin/{DEVICE}/fbink
- Added button to Disable or allow CORE_DUMP. More info in first post.
- Renamed Block Device Logging button to Block Device Logging (not safe)
- Added manual reboot button (removed auto reboot from scripts)
- Added button to migrate from renameotabin

Download is in first post.

[DNSB]

Seems to be working happily here. I did have to run renameotabin to allow OTA updates before I saw the enable/disable OTA updates button. Makes sense since the renamed OTA binaries would not be seen by BinaryRenamer with it's different renaming scheme. (PW4 (10th gen, FW:5.18.1).

[juliazero]

I released 2.0 version again. I added manual reboot button (removed auto reboot from scripts) and button to migrate from renameotabin