K5 Collections Manager

[NiLuJe]

@ixtab: Err, you got the wrong file, I did repack usbnet for the PW (that's from a download from the post, to check that I didn't simply upload the wrong package ^^):

Checking update package update_simple_usbnet_1.1_install.bin
Bundle         SP01
Cert number    0
Cert file      pubdevkey01.pem
Bundle         FD04
Bundle Type    OTA V2
Minimum OTA    0
Target OTA     18446744073709551615
Devices        5
Device         Kindle 5 Touch Wifi
Device         Kindle 5 Touch Wifi+3G
Device         Kindle 5 Touch Wifi+3G Europe
Device         Kindle PaperWhite Wifi
Device         Kindle PaperWhite Wifi+3G
Critical       0
Padding Byte   0 (0x00)
MD5 Hash       aea19ffb35240c2e9275135e19fcbf07
Metadata       0

:?

That's confirmed by the name of the bundlefile in your log:

update-simple_usbnet-install.dat

That's what the python packer did (that Yifan tweaked to build his first few K5 packages).
KindleTool always uses update-filelist.dat .

[ixtab]

Originally Posted by ixtab

This is a question for the people who already own a Paperwhite, and who are adventurous enough to try this...

Collections Manager should be far less firmware-version-dependent than, for instance, JBPatch. In fact, it might work out of the box on Paperwhites. At least, substituting the Amazon libraries on the build path with the files from FW 5.2.0 (instead of FW 5.1.2) does not produce any compile errors, so it might actually just work.

To test it, you will need:
- the developer keys - need to be manually installed
- the Kindlet jailbreak (manually install it as outlined in the src/ folder) - this should install without any problems; the original file is the same on the Touch and PW.
- and of course the .azw2 file from the first post.

I would be interested to know whether it works, or if it doesn't, which errors it produces. In case of hangs or crashes, more information is available either in the system log, or in /mnt/us/developer/Collections Manager/work/ (well, at least, that's where logs go on the Kindle Touch).

Anyone?

So... a little update:

- I now repackaged the Kindlet Jailbreak package, so that it can (also) be installed on the Paperwhite. You can download it here. This file should be SAFE to install/uninstall on your Paperwhite. And while you will not see any noticeable effect of the install or uninstall, please let me know if it succeeded (=rebooted and brought you back to the normal UI without any error).

- Since the Kindlet Jailbreak now has a package for installation, only the developer keys still have to be manually installed.

- a working usbnetwork package (which is required to get root access for manually installing the other dependencies) can be obtained from this thread.

Any feedback is very welcome.

[ixtab]

Originally Posted by NiLuJe

@ixtab: Err, you got the wrong file

Hmpf. Too many files with the same name

But yes, I obviously got something wrong, and you're right. I'll try to fix my posts now.

[NiLuJe]

@ixtab: I didn't want to change the version number, but maybe I will, that might help avoid stuff like this .

[ecksor]

Originally Posted by ixtab

So... a little update:

- I now repackaged the Kindlet Jailbreak package, so that it can (also) be installed on the Paperwhite. You can download it here. This file should be SAFE to install/uninstall on your Paperwhite. And while you will not see any noticeable effect of the install or uninstall, please let me know if it succeeded (=rebooted and brought you back to the normal UI without any error).

- Since the Kindlet Jailbreak now has a package for installation, only the developer keys still have to be manually installed.

- a working usbnetwork package (which is required to get root access for manually installing the other dependencies) can be obtained from this thread.

Any feedback is very welcome.

Installed and uninstalled. Worked perfect, no errors.

[blueshiftlabs]

I was able to install Kindlet Jailbreak, get usbnet running, SSH into the device, and install the dev keys. After that, installing Collections Manager was pretty simple.

When I ran it, it got stuck at the "www.ixtab.tk" splash screen. The log was full of multiple copies of this exception trace:

[10/7/12 5:21 PM] Collections Manager (v. 1.3.3)

java.lang.NoClassDefFoundError: com.amazon.kindle.booklet.ChromeException
        at com.mobileread.ixtab.collman.CollectionManagerKindlet.initUiAfterSplash(CollectionManagerKindlet.java:70)
        at com.mobileread.ixtab.collman.CollectionManagerKindlet.access$1(CollectionManagerKindlet.java:66)
        at com.mobileread.ixtab.collman.CollectionManagerKindlet$2.run(CollectionManagerKindlet.java:51)
        at java.awt.event.InvocationEvent.dispatch(Compiled Method)(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Compiled Method)(Unknown Source)
        at java.awt.EventQueueProxy.dispatchEvent(Compiled Method)(Unknown Source)
        at java.awt.AGUIEventDispatchThread.pumpOneEventForHierarchy(Compiled Method)(Unknown Source)
        at java.awt.AGUIEventDispatchThread.pumpEventsForHierarchy(Compiled Method)(Unknown Source)
        at java.awt.AGUIEventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)
        at java.lang.Thread.startup(Unknown Source)

[hfpop]

Hello,

Does this work on the new Kindle PW as well?

[knc1]

Originally Posted by hfpop

Hello,

Does this work on the new Kindle PW as well?

Answer in the post directly above yours: No.

[hfpop]

Originally Posted by knc1

Answer in the post directly above yours: No.

Thank you. It was not obvious for me that the error that user had was on the Kindle PW.

[ixtab]

@blueshiftlabs: Thanks for testing it, and sorry that it doesn't work.

In fact, that error got me thinking that my statement "at least it should compile" must have obviously been wrong. And indeed, I had added the 5.2.0 libraries, but forgotten to remove the 5.1.2 ones - stupid me. After removing the 5.1.2 libraries from the project, I now get about 300 compile errors.

Bad, bad Amazon. Their even more aggressive obfuscation now seems to have again renamed classes and methods. This means that porting these things to the PW will be a lot of work, and I don't even know how to do it right now. Anyway, I can't start working on it before I receive my PW.

[aceflor]

@blueshiftlabs : how did you manage to install kindlet and usbnet ? I get an update error 3 each time....

@ixtab: thank you for the work, very appreciated.

[diba]

Amazon did similar on 3.4, renaming files, shifting around codes, just to make us doing work again ...

[ixtab]

Originally Posted by aceflor

@blueshiftlabs : how did you manage to install kindlet and usbnet ? I get an update error 3 each time....

@ixtab: thank you for the work, very appreciated.

Update error 3: you are restarting the device instead of using "Update your Kindle".

I really don't understand why this keeps being asked over and over. The correct method to install updates is described in every single README.txt. Which part of "READ ME" do people not get?

(Sorry, nothing personal. It's just that this question has been answered about a thousand times now).

[aceflor]

Originally Posted by ixtab

Update error 3: you are restarting the device instead of using "Update your Kindle".

I really don't understand why this keeps being asked over and over. The correct method to install updates is described in every single README.txt. Which part of "READ ME" do people not get?

(Sorry, nothing personal. It's just that this question has been answered about a thousand times now).

You are right, I am an idiot.

[ixtab]

Here's a new version.

This version does not contain any new functionality (except for a tiny bugfix which affects the renaming of collections).

So, why has the version been bumped to 1.4.0? Simple: because internally, pretty much everything has changed. All of the code has been completely refactored, to even prepare it for Paperwhite support. If you're curious, here is the massive changeset.

There are major differences between Firmware version 5.1.2 and 5.2.0 (thanks, Amazon, for getting ever more aggressive with the code obfuscation! ).

Note that it still doesn't support the Paperwhite - I have only laid the groundwork for the support, by separating the device-independent from the device-dependent parts. The device-dependent part for 5.2.0 still needs to be done - and this will be some tough work.

Anyway, because of these major code changes, I may well have introduced a few new bugs (well, I don't hope so, but you never know). So please install the new version and let me know if everything works correctly, or if maybe I actually did break something.