MobileRead Forums - Kindle Paperwhite Jailbreak (5.2.0

MobileRead Forums (https://www.mobileread.com/forums/index.php)

- Kindle Developer's Corner (https://www.mobileread.com/forums/forumdisplay.php?f=150)

- - Kindle Paperwhite Jailbreak (5.2.0 - 5.3.1, 5.3.4, 5.3.5) (https://www.mobileread.com/forums/showthread.php?t=198446)

Kindle Paperwhite Jailbreak (5.2.0 - 5.3.1, 5.3.4, 5.3.5)

The preferred jailbreak method is now HERE.

Original post:

Spoiler:

Great news!

I think you should post the "FINAL NOTE TO AMAZON" too:

Final Note to Amazon:

Spoiler:

Code:

FINAL NOTE TO AMAZON

--------------------



I know you are reading this, because that's part of your job :-)



Please, pretty please, keep your products modifiable by those who want to

modify them. The developers are not your enemies - we are your allies.

Pretty much all of the tweaks and hacks are actually there to add useful

functionality to the Kindles, to make them even better devices.



I understand that part of the Kindle's success lies in the simple fact

that it's superior to the competitors' products, and I understand that

you want to keep your trade secrets secret. Maybe that is the reason for

the ever-more aggressive obfuscation of the Java classes.



I also realize that a very small part of the information that was published

in the "dev scene" could be considered as a threat. I'm talking about

the ad removal (i.e., disabling Special Offers without paying the nominal

fee). I have personally published such information previously, and retro-

spectively, I shouldn't have done that. Mea culpa. I removed all of it,

and I'm not going to publish anything on that topic again. I don't want

to jeopardize the entire dev scene for a few bucks.



That said, and getting back to the point: Please don't render this

jailbreak method useless. All of the previous methods could be considered

a real threat (in the sense of "security hole"), because they - at least,

in principle - could have happened without the user noticing it, via

some "drive-by" attack. So it's fair to close those holes.

This method cannot be automatically exploited: the user has to knowingly

and willingly take action before anything happens.



So, to conclude: please don't attack the developers' scene and users who

just want to use the full potential of their Kindle.

Oh, and feel free to incorporate the developer-contributed enhancements

into the stock firmware. Almost all of them are using extremely permissive

licenses.



And, as a very last statement: feel free to contact me at the email address

provided in the README file.



-- ixtab, December 2012.

We want to make reading that easy for them.

Great, thanks a lot! Impressive job, whitehats rulezz 4ever! :)

Me and my Kindle are both soooo grateful :)

:thanks:

great work ixtab :2thumbsup, although i don't own a Paperwhite.

Awesome, you just saved me $120 :D

Quote:

Originally Posted by geekmaster (Post 2327851)

Great news!

I think you should post the "FINAL NOTE TO AMAZON" too:

We want to make reading that easy for them.

Hehe... well, just leave it in your post, it's immediately below the other announcement ;)

Quote:

Originally Posted by dasmoover (Post 2327877)

Awesome, you just saved me $120 :D

How so?

Thank you, ixtab, for your excellent work.

Quote:

Originally Posted by ixtab (Post 2327881)

How so?

It's no longer going in the trash ;)

Thank you.
I can't wait to get home and try it out.

AWESOME, ixtab! I knew that hackers will always win at the end :)

What a great new! Thanks Ixtab!

great work ixtab, and :2thumbsup for the message to amazon in your readme.txt (see, I read it completely ;)). It is a very positive and responsible message you are sending them, I can only hope they will indeed get in contact with you.

@all: thanks to everyone for the positive feedback!

Please note that I just updated the file, so the 70 people who already downloaded it should probably download it again, just to be on the safe side.

The bugfix is really only relevant for people who decided to modify the jailbreak.sh, to disable some of the components. In that case, the components were still installed, even if they shouldn't have been. This is fixed now.

In other words: if you simply used the recommended default settings, nothing went wrong, and there is no need to worry.