Font, ScreenSaver & USBNetwork Hacks for Kindle 2.x, 3.x & 4.x

[the-equinoxe]

Originally Posted by dsmid

I would still address this issue in a dedicated hack.
These emergency features are not something an average user is able to use.

sure, a new jailbreak is needed.
But in the meantime someone with one of these hacks installed, can easily use the emergency.sh scripts to gain "full" control again (install/uninstall by eg. backing up: pubprodkey01 and renaming pubhackkey01 to that name*).
So many possibilities, and personally I am glad the emergency option is available.

Btw placing a emergency.sh in a certain directory is not unlike placing an update*bin in a certain directory..
If the user can't handle placing a certain script in a certain directory, then that same user would also not be able to change the fonts or the screensavers.
just saying..

And yes, not every user can write (safe) shell scripts. I totally agree with that!

[Tiersten]

Originally Posted by the-equinoxe

Btw placing a emergency.sh in a certain directory is not unlike placing an update*bin in a certain directory..

Not quite. The updates are checked to ensure that they're valid unlike the emergency script.

[the-equinoxe]

Originally Posted by Tiersten

Not quite. The updates are checked to ensure that they're valid unlike the emergency script.

I was referring to "These emergency features are not something an average user is able to use. "

BTW did anyone even try to do eg:

#!/bin/sh
export PATH=/usr/sbin:${PATH}

_FUNCTIONS=/etc/rc.d/functions
[ -f ${_FUNCTIONS} ] && . ${_FUNCTIONS}

mntroot rw

#install key
cat <<EOF > /etc/uks/pubprodkey00.pem
-----BEGIN PUBLIC KEY-----
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDJn1jWU+xxVv/eRKfCPR9e47lP
WN2rH33z9QbfnqmCxBRLP6mMjGy6APyycQXg3nPi5fcb75alZo+Oh012HpMe9Lnp
eEgloIdm1E4LOsyrz4kttQtGRlzCErmBGt6+cAVEV86y2phOJ3mLk0Ek9UQXbIUf
rvyJnS2MKLG2cczjlQIDAQAB
-----END PUBLIC KEY-----
EOF

mntroot ro

[Tiersten]

Originally Posted by the-equinoxe

BTW did anyone even try to do eg:

Won't work. As previously mentioned, it only looks for pubprodkey01.pem and pubprodkey02.pem

[the-equinoxe]

Originally Posted by Tiersten

Won't work. As previously mentioned, it only looks for pubprodkey01.pem and pubprodkey02.pem

ok, then backup pubprodkey01.pem and create one with the contents of the hackkey, like I said in an earlier post..

[Tiersten]

Originally Posted by the-equinoxe

ok, then backup pubprodkey01.pem and create one with the contents of the hackkey, like I said in an earlier post..

Do key 1 if you want to disable Amazon updates. Do key 2 if you want to still be able to do Amazon updates. I've never seen them use key 2 and its probably a backup in case they ever lose key 1.

[Tiersten]

Originally Posted by Tiersten

Do key 1 if you want to disable Amazon updates. Do key 2 if you want to still be able to do Amazon updates. I've never seen them use key 2 and its probably a backup in case they ever lose key 1.

Actually, either key would disable updates since the first key would prevent the update from being validated and the second key would fail the hash check of the firmware files. Not much difference between either one in that aspect but replacing the first one is probably better so it fails earlier.

So yeah, ignore this.

[the-equinoxe]

Originally Posted by Tiersten

Actually, either key would disable updates since the first key would prevent the update from being validated and the second key would fail the hash check of the firmware files. Not much difference between either one in that aspect but replacing the first one is probably better so it fails earlier.

So yeah, ignore this.

cool,

[Kindlevarazs]

Hi!

I would like to ask a correct answer: is Amazon pushed 3.1 to Kindles or not? Anybody get this update this way or not? (Manual installing not interesting).
Thank you in advance!

[Tiersten]

Originally Posted by Kindlevarazs

I would like to ask a correct answer: is Amazon pushed 3.1 to Kindles or not?

Yes. Quite a lot of people have said that they've gotten updated to 3.1 automatically.

[dsmid]

Here's the implementation I promised.

[foghat]

How do you uninstall the screen saver, font, and jailbreak?

I copied each unistall file to the root of my kindle and did an update. I did this one at a time. first fonts, then screens savers, the jail break, but nothing seems to have uninstalled. I can still access the screen savers directory and it has my custom screen savers in it.

[foghat]

okay, didn't notice before, but if I turn it off, I do get the dead authors now and the old fonts are being used now. However I can still see and access all the 'system' folders that I cannot see on my wife's kindle which has not been jail broken.

kind of confused right now.

[kranu]

Originally Posted by foghat

okay, didn't notice before, but if I turn it off, I do get the dead authors now and the old fonts are being used now. However I can still see and access all the 'system' folders that I cannot see on my wife's kindle which has not been jail broken.

kind of confused right now.

You have to delete those files yourself, if I recall correctly. It's fine to keep them there though for when a new jailbreak comes out, since you can always delete them later.

[OakIris]

Originally Posted by Tiersten

The hacks themselves are mostly working.

The jailbreak itself which allowed the installation/uninstallation of the hacks however has been broken. This means any hacks you had installed prior to 3.1 can not be currently uninstalled.

The worry is that if an easy method of uninstallation isn't found then a future update may have issues due to the presence of these hacks. Another worry is that these hacks may cause some warranty issues with Amazon but that hasn't actually been proven either way at the moment.

As you're already on 3.1, there is nothing else to do done for now.

I don't want to go back to a vanilla Kindle, but... I take it that the consensus is that the safest thing to do is to uninstall the hack/s and jailbreak before installing the 3.1 firmware, just in case keeping the older jailbreak/hack files (which can no longer be uninstalled after the update) interferes with future firmware updates and/or causes problems with getting warranty service from Amazon?

Personally, I am not that concerned with the warranty issue, but if keeping the old jailbreak/hack on my Kindle and then upgrading to 3.1 might cause problems with future updates I do find that worrying.

Silly conspiracy theory thoughts - do you think Amazon's Kindle developers deliberately added in some sort of script to build in the "can't uninstall jailbreak/hacks" feature to cause problems with those of us naughty enough to want our own screensavers and fonts, or was this just an unintentional consequence? That would teach us and prevent others from going down this same dark path! To my (limited) knowledge, this is the first firmware update that disables the ability of the end user to go back to a "vanilla" set up....

Holly