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

[jetfin]

Have been trying to update my 3.02 to 3.03 manually but it constantly fails even after I removed all my hacks (jb, ss & usb).

The only non-original thing on my k3 at this point is Duokan (oct 16 version) -could that be causing the problem? I don't know chinese, but from google translate i understood that Duokan does not prevent Kindle FW updates...

I'm assuming "reset to factory defaults" will not help me here, but what about recovery menu options?

Any help would be greatly appreciated!

[clotilde]

Thanks for your quick replies, Rinzwind and NiLuJe.

I've tried Rinzwind's image file and it doesn't work either. I do shut down and restart the device every time I make a change to the screensaver folder, and I'm able to verify that the contents of that folder is indeed refreshed when I delete the default screensaver (then I have no screensaver) or copy it back again (then the default screensaver is back).

Here's the strange thing I've discovered: if I take one of my image files and rename it to 00_you_can_delete_me.png, then I am able to transfer it to the screensaver folder, reboot, and have it be my new screensaver.

In short, it looks like the device will only accept that specific filename as a valid screensaver file. (Note: I am using the Kindle 3 Wifi.)

Is there a way to uninstall the hack so I can try installing it again? I've tried using the update_ss_0.15.N_k3w_uninstall.bin and running it like the install file, but it doesn't seem to have any effect.

Many thanks!

[NiLuJe]

@jetfin: No idea about duokan, but check the logs (;dumpMessages) to find which file(s) fail the checksum checks.

@clotilde: The hack doesn't change anything as to how/what file name/types the Kindle handles...

Just to make sure, what are you exactly doing when you 'shut down and restart the device'? Because I'm talking about a full restart (ie. Settings => Restart, not just flicking the power switch off & on) or a framework restart via the autoreboot feature of the hack.

[jetfin]

@NiLuJe: Thanks for the tip!

101021:235835 system: I otaup:def:processing update /mnt/base-us/system/update.2348/06/update-06-529960105-536720111.bin
101021:235835 system: I otaup:def:version is "FC02"
101021:235836 system: I otaup:def:update image checksum OK
101021:235836 system: I otaup:def:drawing: eips 36 38 "stage 1 of 2"
101021:235837 system: I mntroot:def:Making root filesystem writeable
101021:235837 ota_install: I def:patch:tune2fs=0:disable autocheck success
101021:235838 ota_install: I def:patch:patchinfo="/bin/busybox":patching file
101021:235838 ota_install: I def:patch:patchinfo="/etc/epoch.txt":patching file
101021:235838 ota_install: I def:patch:patchinfo="/etc/init.d/filesystems":patching file
101021:235838 ota_install: I def:patch:patchinfo="/etc/prettyversion.txt":patching file
101021:235838 ota_install: I def:patch:patchinfo="/etc/sysconfig/iptables":patching file
101021:235838 ota_install: C def:patch:patchinfo="/etc/sysconfig/iptables":checksum failure
101021:235838 ota_install: I def:patch:current_md5=319c76b5985baeaf1f64ec9f8eb595be,expected_md5=c5854fe5414a78ae2e14f35386228ea8,patch_md5=5ac917d7987d5a0e218fcf04cf5adb9c:checksum verify
101021:235842 system: E otaup:def:image update failed

So it looks like it's iptables? -pretty sure i did not edit it....

So now i need to get iptables back to it's virgin 3.02 state....

Anybody have an original k3g (B006) 3.02 iptables?

update: had a copy of my root fs and just checked iptables and it looks identical to the one i have now... -i definitely never touched it...

[jetfin]

just verified that md5 of iptables from my fs copy is same as one that failed the checksum...

Now what?!

[NiLuJe]

The 'current_md5' md5sum in the logfile is the md5sum *after* bspatch (when the patch fails because of a checksum mismatch, it's probably the same checksum as *before*, though, AFAIR, bspatch gives up on a checksum error).
'expected_md5' is the correct md5sum of the patched file (ie. at v3.0.3)
'patch_md5' the md5sum of the patchfile.

The correct md5sum of this file from a vanilla 3.0.2 install is actually
de56a93374824125a600e3f8bbb08957

(You can confirm this with a grep etc/sysconfig/iptables /test/diags/factory/rootfs_md5_list)

Check this post for a working file from a vanilla 3.0.2 dump.

So, yeah, it does look like your file has been modified .

[jetfin]

Merci mon ami!

Updated successfully to 3.03!

-I'll be making a LOT more backups often after this...

[Balerion]

Hi all,

just thought I'd provide the shortcut I use to copy paste and rename the autoreboot file into reboot, all with just a single click (win7) or a double-click (XP, Vista).

Just do the following (on your desktop or wherever).

1) RIGHT-click an empty space, and go to NEW ---> SHORTCUT

2) In the target location box type the following...

(Windows Installation Hard Drive Letter):\Windows\System32\cmd.exe[single-space]/c[single-space]copy[single-space][kindle drive letter]:\linkfonts\autoreboot[single-space][kindle drive letter]:\linkfonts\reboot

Example:

C:\Windows\System32\cmd.exe /c copy D:\linkfonts\autoreboot D:\linkfonts\reboot

NOTE... make sure you put [forward-slash]c just before the copy command and not a backslash, or you can just copy and paste the above, replacing the D with your Kindle's drive letter

3) click NEXT, name your new shortcut and click FINISH. tada!

4) change the icon if you want by RIGHT-clicking your shortcut, going to PROPERTIES, select CHANGE ICON, browse and select a new icon, OK, APPLY it, OK... you're done.

Now the application of the reboot file is just a double-click away or a single-click if you have win7 (pin to taskbar) or an app launcher\dock program like rocketdock or objectdock.

Just repeat the process for the screensaver but replace linkfonts with linkss

I also found a tiny app to eject the Kindle in the same way... just a single-click or double-click, rather than the OPEN EXPLORER, RIGHT-CLICK Kindle drive letter and select EJECT method... here

Hope that's useful to some people

[clotilde]

Thank you NiLuJe -- the full restart was the problem, it works perfectly now. As a new Kindle user, I didn't know about the Settings > Restart function, and was merely turning it off and on again.

If I may make a suggestion, perhaps this is something you could add to the instructions to clarify for other new users?

Thanks again for the hacks, and for the prompt and helpful replies!

Clotilde.

[daffy4u]

Originally Posted by clotilde

Thank you NiLuJe -- the full restart was the problem, it works perfectly now. As a new Kindle user, I didn't know about the Settings > Restart function, and was merely turning it off and on again.

If I may make a suggestion, perhaps this is something you could add to the instructions to clarify for other new users?

Thanks again for the hacks, and for the prompt and helpful replies!

Clotilde.

There are instructions for this in the Visual Kindle Guide wiki which is also linked in the first post. The wiki has step by step instructions with pictures for both the Screensaver and Font hacks.

NiLuJe, maybe you could make that link more prominent.

[clotilde]

And actually, re-reading the original post now, I realize that NiLuJe had spelled out the full Settings > Restart instructions in the jailbreaking section -- I simply missed it. There's a lot of info in there!

[TallMomof2]

I updated to 3.03 first and then applied the jailbreak and the ss hack. Worked perfectly, many thanks!

[Calleja]

Hey! I love the screensavers hack! I'm having an issue, though, and I tried searching the thread for it in case it was already answered but 65 pages seemed a bit much O_O

I'm not getting a random sequence. I've created the blank "random" file in the linkss folder in my Kindle 2, but I still get the exact same sequence of screensavers on every boot.. even a boot created by the "reboot" blank file technique. Any ideas?

[NiLuJe]

@Calleja: Check the filenames of your images, if they haven't been changed to N_X (Where N is a 5-digit number, and X the usual filename), then you messed up the 'random' file .

It'll only be randomized during a full boot (or after an update) though, *NOT* when doing a framework restart (ie. the 'reboot' file), that'll just reset the list to the beginning.

[Calleja]

Oh.. how do I do a full boot then? The file names are not being changed, no.

What did I mess up? I just copy pasted one of the other blank files, renamed it to "random" and left it there, exactly as I do with the reboot one and it always works.