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

[Pushka]

Originally Posted by bonaina

Thanks alot for the replies.

@Nijule The source of the book is Amazon and it maybe their mistake. I'll try redownloading it.

@pushka when you mean hard restart, do you mean just restarting it through settings? or did you reset it to factory default?

I restarted by holding the wake button until everything started flashing, and then released it. Factory default is the last thing you would try after all else had failed.

[dcon]

Sorry if this has been mentioned, I've tried finding it with no success.. but how do we get rid of your defualt screensaver once it is hacked? I only have a few custom screens I like to use, and really don't want every 3rd or 4th time I power down to see the congratulatory message on hacking my Kindle

Thanks for all your work on these hacks..

[gargoyle67]

Originally Posted by 911jason

The hacks and firmware are not affected by firmware upgrades (at least, not yet!) and you can see the link in my sig for over a thousand screensaver images.

Great, Thanks Jason

[drendo70]

NiLuJe, anyway I can run RSYNC once every 10 minutes (CRON???) to check a remote server (and just fail hard if there is no net connection...?) could be a good interim solution

[intruderukr]

I just got a used Kindle 2 international (serial number BOO3...). I intend to use it mainly for reading Ukrainian ebooks. First I did the 2.5 update, then I copied 'update_jailbreak_k2i_install.bin as instructed, but after properly disconnecting the kindle from the usb, pushing the menu key there is no update option. I tried the other update_jailbreak files in case I had the wrong one, all to no avail. Is there any help for me?
Thanks, Intruderukr

[NiLuJe]

@dcon: You might want to re-read the first post and/or the wiki.

@intruderukr: Are you sure you put the binfile in the right place?

[Ezh]

Hello there,

Can one use Kindle 3 fonts on Kindle 2 (I assume they are unicode)?

[NiLuJe]

@Ezh: Yes.

Updated the ScreenSavers Hack to v0.12.N. Finally ditched my crappy "random" implementation. It's now much more robust, truly random, and dumb sort friendly (fixed length zero padding).

If you're not using the random feature, there's no need to update .

EDIT: Er, wait. I probably broke (again ) the sorting of files with spaces/special characters in them...

[NiLuJe]

Yep, Updated the ScreenSavers Hack to v0.13.N. Fixed the randomizer to properly handle spaces in filenames again. Sorry :/.

[flandroid]

Thanks, I always use the randomiser.

Do I need to uninstall the old one first?

edit: eh, i'm doing it anyway, can't hurt. i did notice these .bins are considerably larger, though, my goodness.

[NiLuJe]

@flandroid: Nope, no need to uninstall first . And yeah, automatically installing the link* directories, and stuffing them with statically linked C binaries, has dramatically increased the size of the binfiles... . Wait 'till you see the K3 Fonts hack... >_<".

[[Ahmed]]

Originally Posted by NiLuJe

Wait 'till you see the K3 Fonts hack... >_<".

leave a little space so we can still have one or two books on our kindles.

[911jason]

@NiLuJe

I just installed the SS v0.13.n and I see that all of my screensaver images have been renamed with leading 00001_, 00002_, 00003_, etc. Do I still need to add the "random" file?

[joblack]

Okay I got a problem. I have enabled the auto option for the usbnetwork but I can't connect to it and I can't access the the kindle drive either.

How can I disable the usbNetwork if it's alread running?

[NiLuJe]

@911jason: That's the new randomizer. Unless I did something very dumb, I assume you already had the "random" file if it did this! :P

@joblack: Restart in recovery mode, and kill the trigger file over USB MS, maybe? (holding [HOME] during boot). If you still can't remove it, craft a simple update file to remove the trigger file.

Quick update: I'm currently testing/debugging the K3 fonts hack. So far: I didn't break the K2 support. Classic system-wide fonts works. Browser handling is broken, and I'm currently trying to coerce fontconfig into submission to fix it.