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

[kranu]

Originally Posted by omk

Can anyone confirm or deny if the 3.1 update breaks SSTimeOut 0.2 ?

(Jailbroke a 3.0.2, updated to 3.0.3 and installed SSTimeOut, usb, and screensavers)

Thanks,
Martin

SSTimeout works fine for my K3.1G

[icedtea32]

Originally Posted by Kindol

Do you still have this problem Re: EDIT?

I had similar problem but after reading here I managed to put together what has been discussed in different posts and solve same problem like the one you had/have.

I thought was just me happened to have that problem coz no one else mentioned here (or may be I havent read all the posts)

anyway let me know.

apoligies for my English...not my native language

hi i have the same problem. i tried updating the default font-hack to another font type and now i can't get into the settings menu to run an update. please help!!

thank you.

[omk]

Thanks, didn't see your reply but went ahead and upgraded once I satisfied myself I could manually edit the t1_timeout file if needed.

I applied the full Update_kindle_3.1_B006.bin from AZ, not the incremental file pushed out to me, since that one was known to not break usb.

[chilady1]

Originally Posted by rogerinnyc

They do for me. I installed 3.1 over 3.0.3 on my K3 (3g) with the Screensaver Hack and the Fonts Hack already installed. It took a long time to install (lots of restarts), but finally came to rest on the home screen. Everything is working fine, and it's very nice to have page numbers AND my (well, Nulije's) Hacks.

I second this, I have had a jailbreak from a while ago and I just recently updated my K3 to 3.1 and my screensaver hack is still working. I don't have the font hack on so can't speak to that but screensaver is working fine.

As a matter of fact, I have been wondering for the past few days why everyone has been asking about a newer version of jailbreak for the Kindle - I couldn't understand when people talked about 3.1 breaking the jailbreak hack cause mine is working fine. I am sure the smart people here will figure this out. Do I need to be (1) worried about anything and (2) do anything?

[Tiersten]

Originally Posted by chilady1

As a matter of fact, I have been wondering for the past few days why everyone has been asking about a newer version of jailbreak for the Kindle - I couldn't understand when people talked about 3.1 breaking the jailbreak hack cause mine is working fine. I am sure the smart people here will figure this out. Do I need to be (1) worried about anything and (2) do anything?

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.

[chilady1]

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.

Thank you so much for the quick answer. I will patiently wait for folks smarter than me to figure this out.

[ths]

Correct me if I'm wrong - I'm just getting started here - but for users who installed the font and/or screensaver hacks before upgrading to 3.1, shouldn't it be possible to uninstall those hacks, and/or re-jailbreak the device, using the "emergency script" mechanism that those hacks provide?

I don't know enough yet about the internals to trust myself to write such a script, but it seems like it should not be too difficult.

[dsmid]

Originally Posted by ths

I don't know enough yet about the internals to trust myself to write such a script, but it seems like it should not be too difficult.

Good idea, I'm going to implement it if no one else takes on the challenge.

[kranu]

Originally Posted by dsmid

Good idea, I'm going to implement it if no one else takes on the challenge.

Just wondering, what is this emergency script mechanism? I've never heard of it before =/

[dsmid]

Originally Posted by kranu

Just wondering, what is this emergency script mechanism? I've never heard of it before =/

It's been just invented by ths, that's why you've never heard of it before
My implementation would just start a script when Kindle starts and that script would check settings in some user store subdirectory and then it would install either Amazon or hack certificate. In this way you would be able to switch the updates provider via USB storage.

[ths]

Originally Posted by dsmid

It's been just invented by ths, that's why you've never heard of it before

Haha, not quite. From what I can tell, it's an undocumented feature that's already built into those hacks: if you put a file called 'emergency.sh' in the correct directory, it will run that script at boot time, instead of the normal hack startup script. It's intended for emergencies (obviously), and it would be very easy to seriously break stuff if the script is buggy.

My point was that, in the absence of a normal, working jailbreak, this would be one way to regain root access. It's not a process I'd recommend if you can avoid it, and it's no substitute for a true 3.1 jailbreak.

[olterman]

Hmmm, I hacked my kindle an, I have installed the SS hack (no fonts though) and I did the 3.1 upgrade without thinking and for me everything works. The 3.1 with pagenumbers and my custom screensavers etc ...

[the-equinoxe]

Originally Posted by dsmid

It's been just invented by ths, that's why you've never heard of it before
My implementation would just sta

Funny, but the reality is:
I found the feature in: linkfonts, linkss and usbnet

eg.:

USBNET_BASEDIR="/mnt/us/usbnet"
USBNET_BINDIR="${USBNET_BASEDIR}/bin"
USBNET_EMERGENCY="${USBNET_BINDIR}/emergency.sh"
...
{USBNET_EMERGENCY}
                        # Run it...
                        ${USBNET_EMERGENCY}
                        # And GET OUT! NOW!
                        exit 0
                fi
                # Everything's fine, yeepee.

[dsmid]

Originally Posted by the-equinoxe

Funny, but the reality is:
I found the feature in: linkfonts, linkss and usbnet

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

[Tiersten]

Originally Posted by the-equinoxe

Funny, but the reality is:
I found the feature in: linkfonts, linkss and usbnet

Its still not recommended to update to 3.1 if you do care about hacks. If you read some of the earlier posts when 3.1 came out, the idea was presented that we use a similar mechanism to this for people who aren't already on 3.1 so they've got a backdoor into the Kindle once they do update to 3.1.

Piggybacking off these hacks to provide an uninstallation method is dangerous due to the one shot deal nature of the uninstallation script. It'd have to do be done properly by making the above backdoor unless you're willing to deal with support hell.