Kindle 3.1 Jailbreak

[yifanlu]

Originally Posted by SeeeeJaaaay

I was wondering if anyone would give a simple - for the end user (i.e. no knowledge of programming) - step by step instruction on how to jailbreak and install usbNetwork for using the kindle as a wifi modem. I have seen some step by steps, but they are not simple enough. They make assumptions that I know what they are refuring to and don't take time to explain. If some one has already made a step-by-step or even a video, plz direct my there in a reply. Better yet, email me at Seeeejaaaay@gmail.com.

No offense intended, but if you do not know how to install usbnetwork, you shouldn't be messing with it. On the K3, the only use for usbnet is SSH, and I bricked my kindle more then a couple of times in SSH, so others should't even go near it.

[bluesplayer]

YiFanLu

Questions because I AM confused after installing your .4 JB:

1. How can I tell WHICH version of your JB (if any) is ACTUALY installed? What can I look at, or drill down to using USB connection, to confirm?

2. Now with no need for a “ENABLE_HACKS_UPDATES” file in the root - I am unclear HOW this will prevent an Amazon firmware update (or turn it back on so Amazon firmware update can occur). What is I have to do or undo?

Background:
Had old JB (NiLuJe JB 0.4 for Kindle OS 3.0.3.) and SS (.15n) installed and along came Kindle OS 3.1 before I could uninstall JB and SS. But apparently no issues as I mentioned in a previous post – Screen savers still there and seems to work fine.

Because I am preparing for the day I update (if I do ) my mother’s Kindle with Yifan Lu’s JB so I can control if/when an Amazon firmware is pushed/installed before I can get to her Kindle to do whatever I need to (like uninstall a JB) I wanted to see what happened on my Kindle when I installed Yifan Lu’s new JB> By the way it is unfortunate that each of you are calling you hack’s “Jailbreak.” I am sure novices and casual PC/Mac users might get a little confused maybe they should have unique Jailbreak names like JB-Y (for Yifan Lu’s ) and JB-N (for NiLuJe’s) or some other naming convention.

In any case, I installed Yifans newer JB (.3) then installed .4 over that and each SEEMED to install fine (no errors, said it installed, and my Kindle did a restart and the .bin file disappeared from the USB root directory) and my Kindle is working and MY screen savers are still there and working.

Thanks

[dsmid]

Yifanlu, maybe you should reintroduce the “ENABLE_HACKS_UPDATES” functionality (a neat bonus not turned on by default, meaning "do not install any updates from Amazon") to avoid confusion and stay API-compatible with NiLuJe's jailbreak.

[Snakey]

I was pleased with the feature that blocked official Amazon updates. If 0.4 no longer has this feature I will stick with 0.3 for sure.

[yifanlu]

Originally Posted by dsmid

Yifanlu, maybe you should reintroduce the “ENABLE_HACKS_UPDATES” functionality (a neat bonus not turned on by default, meaning "do not install any updates from Amazon") to avoid confusion and stay API-compatible with NiLuJe's jailbreak.

Well, I think only a small two or three people actually don't want to upgrade to 3.1. Most people will find a transparent, no-setup jailbreak more useful. They will find it confusing. They can always install your update provider hack if they want to stay at 3.0.3.

[greyTraveler]

Originally Posted by dsmid

Yifanlu, maybe you should reintroduce the “ENABLE_HACKS_UPDATES” functionality (a neat bonus not turned on by default, meaning "do not install any updates from Amazon") to avoid confusion and stay API-compatible with NiLuJe's jailbreak.

...i s Yifanlu's automatic key checking, with the ENABLE_HACKS_UPDATES file respected, but not on by default. I'm fine w/ the 3.1 update, but I'm not sure I'll be ok w/ 3.1.05; and I'd rather the chance to decide before it gets installed.

And for anyone who just wants simple, then they simply don't create the enable hacks file, and things are completely transparent.

Grey Traveler

[FF2]

Originally Posted by greyTraveler

...i s Yifanlu's automatic key checking, with the ENABLE_HACKS_UPDATES file respected, but not on by default. I'm fine w/ the 3.1 update, but I'm not sure I'll be ok w/ 3.1.05; and I'd rather the chance to decide before it gets installed.

And for anyone who just wants simple, then they simply don't create the enable hacks file, and things are completely transparent.

Grey Traveler

I agree that it would be good to have a way to block the upgrade after 3.1. At least, block it until the user is sure that Amazon did not do something that locks in a jailbreak/hack and gives users a chance to cleanly UNinstall the jailbreak/hacks. Amazon's 3.1 came on rather suddenly - even while it was listed as still in beta folks were getting it automatically and could not UNinstall the hacks.

So a method that allows the user the choice or, at least, delay the timing would be nice.

[NiLuJe]

Keeping Whispernet off is a pretty good way to avoid official updates... (Just sayin' ;p).

I'm pretty much of the same mind as yifanlu on the subject (that's why the enable_hack support is somewhat undocumented in my version).

I'm not really worried about hacked Kindles doing 'new' updates, once it's hacked, for all intents and purposes, we're in, we'll most likely always be able to alter the system one way or another, even without a jailbreak/a working otaup.

[bluesplayer]

Originally Posted by greyTraveler

...i s Yifanlu's automatic key checking, with the ENABLE_HACKS_UPDATES file respected, but not on by default. I'm fine w/ the 3.1 update, but I'm not sure I'll be ok w/ 3.1.05; and I'd rather the chance to decide before it gets installed.

And for anyone who just wants simple, then they simply don't create the enable hacks file, and things are completely transparent.

Grey Traveler

DITTO - that was the bottomline of my long winded post

[janvanmaar]

And for anyone who just wants simple, then they simply don't create the enable hacks file, and things are completely transparent.

I agree with Grey Traveler. Transparent for users who do not care but an option to disable automatic updates for users who want it would be great!

I'm not really worried about hacked Kindles doing 'new' updates, once it's hacked, for all intents and purposes, we're in

It is not just a question of being in/out - there are many other reasons why people opt not to upgrade or upgrade when they want - not wishing new functionalities (social networks integration crap), avoiding newly introduced bugs/regressions or simply wanting to be in control of their own device...

I think only a small two or three people actually don't want to upgrade to 3.1.

Actually, I believe there are many people who prefer to be in control of whether/when to upgrade... Every upgrade may break things that are working with the previous version and there is no simple way to downgrade. For instance, I know of several people (incl. me) who disabled 3.1 update because of this specific problem and several people who regret that they did not disable it and have to suffer by it:
https://www.mobileread.com/forums/sho...d.php?t=123231

[NiLuJe]

@janvanmaar: What I meant to say is that I feel it's an out of scope feature for a jailbreak, whose point is to allow custom updates to install, not block official updates .

[janvanmaar]

@NiLuJe: Got it now
That makes sense indeed.
I just remembered there were issues between jailbreak and the update provider hack but I did not realize that the issues would be gone once the jailbreak does not provide this functionality...
Although, as long as ENABLE_HACKS_UPDATES will be supported, I will probably still prefer to use that just because of my laziness

[NiLuJe]

@janvanmaar: Yep, my version still 'supports' ENABLE_HACKS_UPDATES because, given how it currently works, that was literally a matter of two lines to handle it, but if it weren't for that, I wouldn't have gone out of my way to implement it . (Besides, I'd qualify the fact that it blocks official updates as a side-effect, that's not really the cleanest way in the world to block official updates... ^^).

[yifanlu]

Originally Posted by NiLuJe

@janvanmaar: What I meant to say is that I feel it's an out of scope feature for a jailbreak, whose point is to allow custom updates to install, not block official updates .

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.

[FF2]

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, please include it somewhere - 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.