Kindle 3.1 Jailbreak

[silasgreenback]

Originally Posted by FF2

...I am still awaiting repercussions from the NO-LOG hack (if the NoLog is working). I expect Bezos to trot the approx 2 miles to my house from their new headquarters and personally tromp all over my k3.

[greyTraveler]

Originally Posted by yifanlu

Exactly. I don't want the jailbreak to be a bundle of customizations. People can install additional hacks after the jailbreak, like the change update provider. If people REALLY need a no-update hack, I can modify my no-amazon-logging hack to include this feature.

Yes, that is better. Now that I understand the motivation, I understand that software benifits from being single purpose, and I imagine a jail break even more so.

So I retract all my complaining.

Gray Traveler

[bluesplayer]

Actually not complaining but in my ignorance I guess I didn't (do not ?) get it.

SO do I take these comments to mean with your current .4 JB I can STILL put a ENABLE_HACK_UPDATES empty file in the root and it will keep the next version of an AMAZON firmware push form installing (until I remove the ENABLE_HACK_UPDATES file)?


Second question to anyone who knows: still trying to find out how (if) you can tell what/which JB or version thereof is installed

Thanks
Larry

[bluesplayer]

Actually not complaining but in my ignorance I guess I didn't (do not ?) get it.

SO do I take these comments to mean with your current .4 JB I can STILL put a ENABLE_HACK_UPDATES empty file in the root and it will keep the next version of an AMAZON firmware push form installing (until I remove the ENABLE_HACK_UPDATES file)?


Second question to anyone who knows: still trying to find out how (if) you can tell what/which JB or version thereof is installed

Thanks
Larry

[Kindle3w_Pdfs]

First, let me add my voice to those of other Kindle owners who like the "disable updates" feature... There are more than two or three of us who want to prevent Amazon from modifying our Kindles whenever Amazon chooses (without having to turn off our Kindle's wireless connectivity forever).

We don't necessarily need to disable updates, as long as we can disable auto-updates.

We don't need the autoupdate-disabling hack to be bundled with a jailbreak hack. Ideally it should be an independent hack all by itself. For the same reason that it shouldn't be bundled with a jailbreak, it shouldn't be bundled with any other hack.

Also, I (and others too, clearly) want to be able to save a copy of our Kindle's firmware to a file on our pc, and later restore it from pc back to Kindle. This would allow us to experiment with Amazon updates and 3rd party hacks and then rollback if not satisfied. (If this can already be done using existing hacks; then all that's needed are clear instructions: which hacks are required, and the procedures for saving & restoring the Kindle's firmware.)

Of course, the ability to restore the older firmware must be robust so that an Amazon update (or malicious 3rd party hack) can't modify the Kindle in a way that blocks the restoring process. I don't have the expertise to suggest how that might be done, but I'm wondering if a "sandbox" hack could be created, so that Amazon updates and 3rd party hacks could be installed without risk that they can't be uninstalled and their effects undone?

If users can be confident they can rollback their Kindles, they won't need to disable updates.

Another value of a sandbox hack would be to block trojan functionality that might be embedded in some other seemingly innocent hack (screensaver, fonts, whatever). For example, I wouldn't want a trojan to be able to turn on my Kindle's wireless in the middle of the night and upload information to a hacker.

Thanks for considering this, and best wishes!

[Tanga]

Sorry for the info overload, but I'm a noob at this kind of thing and don't know what might help people help me (if that's even possible).

Thanks in advance!




I guess I should have done more reading before jailbreaking my Kindle. I JBd it with the express purpose of playing Interactive Fiction on it, and so used Andrew's instructions here:
http://adq.livejournal.com/108011.html

Though I used the 0.6N jailbreak from the site he linked, as it was the most recent. Not recent enough it seemed.

It worked for a while, but then froze when I logged into wireless. I restarted it, no problem, but KIF didn't work (an error message saying something about there being an incorrect date). I reinstalled the devkeys and KIF worked again, briefly, but my Kindle froze again (I can't remember what I was doing at the time - I think it was just sitting there while I did something else). This time a simple reset didn't help and I had to do the hard reset (15+ seconds holding the 'on' button).

I think this may have been the point where my Kindle updated to 3.1 - it is 3.1 now at any rate.

Tried to play KIF fail (this time I got an error message about not having the right permissions and to get permission keys from the developer).
Tried to reinstall the devkeys that KIF needed - fail.
Tried to uninstall 0.6N - fail

Tried to do any damn thing?

Kindle says No.

I've tried to install Yifan.lu's hack - but this fails too.

Any suggestions or am I stuck with a un-hackable Kindle.

I am using Ubuntu on my computer (if that's relevant, I can log into XP if needed). Is there any way I can fix this? If someone has a copy of the vanilla system (preferably pre 3.1) can I get this from them and install it? Anyone willing to torrent, or send that?

[NiLuJe]

The freezes are pretty much irrelevant, there's nothing even remotely tinkering with anything that could cause this kind of stuff in a jailbreak. Can't speak for KIF, though, but I've personnally never had any issue with it .

I'm assuming you originally weren't running FW 3.1, but got the update somewhere along the way? That shouldn't be an issue, the jailbreak you used does handle FW 3.1 fine.

So, there's only one question left: What *exactly* do you mean by 'fail'? U007 error? 0003 error? Something else?

And, no, a downgrade is not (easily) feasible.

[bluesplayer]

Yifan Li

Does your JB put a "Update_xxxxxxx_xxxxxx.bin" file in the Linkss folder? I just noticed this file when cleaning up - plus it is not a small file as Kindle files go it is over 7MB!

[here xxxx is just a series of numbers (maybe versions?)]

If not your .4 JB how about your .3 JB? Since I uninstalled your .4 and reinstalled your .3 JB.

I did that so I could block further Amazon pushes with the ENABLE_HACKS_UDATE file/method because of my logistical need to halt Amazon firmware updates - until I can travel to other locations to "patch" other Kindles for folks who cannot)

or anyone who knows the use/need for that file I'd appreciate some insight to source and purpose

Thanks
Larry

[NiLuJe]

@bluesplayer: Nope, that's the Fonts/SS hacks trapping official update files.

[bluesplayer]

Originally Posted by NiLuJe

@bluesplayer: Nope, that's the Fonts/SS hacks trapping official update files.

Again thanks - NOW I am up to date on everything
Larry

[Tanga]

It may have been KIF, or I also added the fonts hack.

0.6 should handle 3.1? If so then why won't the devkeys hack work? I get the 007 error every time.

PS - I presume it's the devkeys hack that isn't working, as I get an error message saying I don't have the correct permissions to be running KIF?

EDIT: The Blog - http://adq.livejournal.com/108011.html
The Devkeys - http://code.google.com/p/adqmisc/dow...evkeys-0.2.zip

[Tanga]

PPS - Is the reason the yifan.lu wouldn't work because I had the 0.6N hack installed? I seem to remember reading somewhere that it wouldn't install over the top of the 0.5?

[NiLuJe]

@Tanga: Type ;dumpMessage in the searchbox, and attach the file created in your documents folder, something's fishy with your setup.

The fonts hack shouldn't cause any issue of that kind either, unless you went the adventurous way and enabled browser fonts support.

Yes, the permissions error when running a dev Kindlet is because you don't have the proper devkeys installed.

And, no, you can't switch jailbreaks without uninstalling it first.

[Tanga]

I'm not really that worried about the freeze - since it hasn't happened since. Most of my books had been uploaded through Calibre anyway, so it wasn't too difficult to re-upload (and re-download my Amazon books from the 'archived items.'

Nope - didn't include browser support for the fonts. The warning put me off, and I don't really use the browser that much anyway.

I just did as you requested, and didn't get any new files show up in my documents folder. I'll try it again. Presumably I should be searching my device?

Can I use another set of dev keys to get compatibility, or do I need to wait for an update from the KIF creator? He doesn't seem too active atm.

EDIT: Long story short, trying to do the ;dumpMessage thing again made my Kindle not show up on USB until I'd reset it and I still didn't get any new docs in my documents folder. Not keen to try that again until I know what's wrong.

007 error on trying to install the devkeys (link to source and files above) again.

[Tanga]

Oh wait - I think I know what part of my problem might be. The files that go along with the the updates are all missing (and folders). What folders / files do I need to go along with the fonts hack?