How to update Kindle 2/DX/DXG with YifanLu's firmware from 3.2.1 to 3.4.2

[budalb]

I applied patch externally. The two text files looks good even though the md5 checksums are different from expected. I hesitate to use the two patched library since there is no way to tell their validity other than md5 checksum. The whole thing seems to run fine without the two original library.

Originally Posted by newman

budalb: Do the patching locally and see what's wrong. CURL and SOUP are probably essential to webreader and browser, but I am not certain since I don't have ldd on my Kindle.

[knc1]

Originally Posted by budalb

- - - -
The whole thing seems to run fine without the two original library.

The system does require those libraries.
Amazon does not ship firmware with extraneous libraries.

What do you mean by "original" in this case of mixed firmwares?
Because you do need those from at least one of the firmwares.

Your finding of "run fine" is only because you haven't tested the features that require them.
(a.k.a: PEBKAC)

[donB006]

Originally Posted by budalb

I tried to update 3.4 to 3.4.2. There are 4 files that had md5 checksum issue.

/etc/version.txt
/etc/prettyversion.txt
/usr/lib/libcurl.so.5.2.0
/usr/lib/libsoup-2.4.so.1.3.0

I skipped those files and updated successfully. The original files have the correct md5 checksum. Any thoughts?

I checked my k3 backup rootfs.img to compare those files. I backed up my k3 when updating from 3.0.2 to 3.1 to 3.3 to 3.4 then 3.4.2. The libsoup have the same file size in 3.4 and 3.4.2 while the libcurl is not the same. The libraries could still be different with the same file size. I don't know why there would have been an md5 error in the Amazon update scripts. Maybe the new libcurl has tls features so that would be important.

kindle keyboard k3 3.4.2

lrwxrwxrwx 1 root root     25 Jul 30  2011 libcurl.so -> /usr/lib/libcurl.so.5.2.0
lrwxrwxrwx 1 root root     25 Jul 30  2011 libcurl.so.5 -> /usr/lib/libcurl.so.5.2.0
-rwxr-xr-x 1 root root 223164 Jun  1  2012 libcurl.so.5.2.0
lrwxrwxrwx 1 root root     20 Dec 27  2010 libsoup-2.4.so -> libsoup-2.4.so.1.3.0
lrwxrwxrwx 1 root root     20 Dec 27  2010 libsoup-2.4.so.1 -> libsoup-2.4.so.1.3.0
-rwxr-xr-x 1 root root 372577 Jun  1  2012 libsoup-2.4.so.1.3.0


kindle keyboard k3 3.4

lrwxrwxrwx 1 root root     25 Jul 30  2011 libcurl.so -> /usr/lib/libcurl.so.5.2.0
lrwxrwxrwx 1 root root     25 Jul 30  2011 libcurl.so.5 -> /usr/lib/libcurl.so.5.2.0
-rwxr-xr-x 1 root root 223144 Sep  1  2012 libcurl.so.5.2.0
lrwxrwxrwx 1 root root     20 Dec 27  2010 libsoup-2.4.so -> libsoup-2.4.so.1.3.0
lrwxrwxrwx 1 root root     20 Dec 27  2010 libsoup-2.4.so.1 -> libsoup-2.4.so.1.3.0
-rwxr-xr-x 1 root root 372577 Jul 30  2011 libsoup-2.4.so.1.3.0

I used linux with mount -t ext3 -o loop rootfs.img /mnt/kindleimg to see the files.

Edit: I just noticed the dates for the libcurl are mixed. I don't know why the 3.4 is 1 Sep 2012 and the 3.4.2 is 1 June 2012. That is wierd.

[knc1]

Originally Posted by donB006

I checked my k3 backup rootfs.img to compare those files. I backed up my k3 when updating from 3.0.2 to 3.1 to 3.3 to 3.4 then 3.4.2. The libsoup have the same file size in 3.4 and 3.4.2 while the libcurl is not the same. The libraries could still be different with the same file size. I don't know why there would have been an md5 error in the Amazon update scripts. Maybe the new libcurl has tls features so that would be important.

kindle keyboard k3 3.4.2

lrwxrwxrwx 1 root root     25 Jul 30  2011 libcurl.so -> /usr/lib/libcurl.so.5.2.0
lrwxrwxrwx 1 root root     25 Jul 30  2011 libcurl.so.5 -> /usr/lib/libcurl.so.5.2.0
-rwxr-xr-x 1 root root 223164 Jun  1  2012 libcurl.so.5.2.0
lrwxrwxrwx 1 root root     20 Dec 27  2010 libsoup-2.4.so -> libsoup-2.4.so.1.3.0
lrwxrwxrwx 1 root root     20 Dec 27  2010 libsoup-2.4.so.1 -> libsoup-2.4.so.1.3.0
-rwxr-xr-x 1 root root 372577 Jun  1  2012 libsoup-2.4.so.1.3.0


kindle keyboard k3 3.4

lrwxrwxrwx 1 root root     25 Jul 30  2011 libcurl.so -> /usr/lib/libcurl.so.5.2.0
lrwxrwxrwx 1 root root     25 Jul 30  2011 libcurl.so.5 -> /usr/lib/libcurl.so.5.2.0
-rwxr-xr-x 1 root root 223144 Sep  1  2012 libcurl.so.5.2.0
lrwxrwxrwx 1 root root     20 Dec 27  2010 libsoup-2.4.so -> libsoup-2.4.so.1.3.0
lrwxrwxrwx 1 root root     20 Dec 27  2010 libsoup-2.4.so.1 -> libsoup-2.4.so.1.3.0
-rwxr-xr-x 1 root root 372577 Jul 30  2011 libsoup-2.4.so.1.3.0

I used linux with mount -t ext3 -o loop rootfs.img /mnt/kindleimg to see the files.

Edit: I just noticed the dates for the libcurl are mixed. I don't know why the 3.4 is 1 Sep 2012 and the 3.4.2 is 1 June 2012. That is wierd.

Use readelf to list both library metadata, and compare that between versions.
They might well be functionally identical.

[donB006]

readelf attached.
Is this what you wanted?

[knc1]

Originally Posted by donB006

readelf attached.
Is this what you wanted?

Well, I didn't want it, but that is exactly what someone needs to find if two different version of a library provide the same features.

And lab126 was nice, they forgot to strip the debug symbols, so their is a lot more than the usual amount of information.
(back in firmware series 3 days, lab126 was still learning how to do this embedded stuff.)

Note: All four listings are concatenated into one file.
Whoever does the comparison(s) will probably have to split that into four files.

[donB006]

There must be a reason the 3.4.2 updater script refused to patch the libcurl and libsoup. There should not have been a problem if the 3.4 files were as expected. My kindle k3 had no errors when updating from 3.4 to 3.4.2 although I didn't check any logs. If the 3.4 libraries are not as expected then they could be found in the pastebin page in the 3.4 rootfs.img
http://pastebin.com/Wdw4L7yT

An easier way might be to send me a PM with an email address and I could attach the two libraries to help. As long as they are for a kindle and not a nook or something.

How effective does the DX function with the 3.4.2 now?

[budalb]

Sorry for typos.

The system runs fine with two v3.4 libraries. I skipped the updates to the two libraries.

Originally Posted by knc1

The system does require those libraries.
Amazon does not ship firmware with extraneous libraries.

What do you mean by "original" in this case of mixed firmwares?
Because you do need those from at least one of the firmwares.

Your finding of "run fine" is only because you haven't tested the features that require them.
(a.k.a: PEBKAC)

[thatworkshop]

Originally Posted by donB006

How effective does the DX function with the 3.4.2 now?

Depends on what you want. I had it and it was Ok, but I reverted back to 2.5.8.
For power issues, you should replace powerd from DX.
For TTS which was critical for me, it's no good and therefore I went back to 2.*

[knc1]

Originally Posted by budalb

Sorry for typos.

The system runs fine with two v3.4 libraries. I skipped the updates to the two libraries.

Ok, now try to connect with the browser to a site that probits SSLv3.
I think the 3.4.2 version is the only one that will allow that.

Then check the logs after you let the device connect to Amazon, they probably now require the newer libcurl when it calls home.

Also, be sure you can read *.azw3 format books (a.k.a: kf-8).
I think that was another change introduced with 3.4.2 version.

[budalb]

I don't access web sites or amazon.com very often. I use it for off line books.

.azw3 is supported since v3.4. It works ok.

Originally Posted by knc1

Ok, now try to connect with the browser to a site that probits SSLv3.
I think the 3.4.2 version is the only one that will allow that.

Then check the logs after you let the device connect to Amazon, they probably now require the newer libcurl when it calls home.

Also, be sure you can read *.azw3 format books (a.k.a: kf-8).
I think that was another change introduced with 3.4.2 version.

[knc1]

Originally Posted by budalb

I don't access web sites or amazon.com very often. I use it for off line books.

.azw3 is supported since v3.4. It works ok.

Your Kindle accesses amazon.com for its own purposes, so check the logs for lib curl related errors.

[newman]

knc1: Thanks, didn't know that about ldd.

bualb:

Which binaries load libsoup-2.4.so?
/usr/bin/browserd
/usr/bin/webreader

Which binaries load libcurl.so?
/usr/sbin/tmd
/usr/sbin/wifid
/usr/bin/curl

So even if you're not interested in TLS, libsoup has to be loadable and functional for you to have KF8/AZW3 since it is rendered by webreader.

The easy way how to test the patched libs may be by mount --bind the patched lib to the system one and restart all the binaries which depend on them (browserd, webreader, ...) and then test KF8 and TLS only web site. Though I am not entirely certain restarting all the affected processes is enough to re-load the respective library... Framework restart may be of some help as well.

[Kaan88]

I can't upgrade to 3.3 because of a different "powerd" file. (checksum error whilte patching) Any idea how I can restore it?

Edit: And I deleted my rootfs backup accidentally. I'm stuck with 3.2.1.
Does anyone have rootfs image for Kindle 2 US? PM me.

[donB006]

Originally Posted by Kaan88

I can't upgrade to 3.3 because of a different "powerd" file. (checksum error whilte patching) Any idea how I can restore it?

Are you sure you are using the correct Amazon update bin? The update would patch the old powerd and then compare the md5 with the expected value. I would suspect your kindle or update technique before the Amazon patching script. Do you remember altering the /usr/bin/powerd or the /etc/init.d/powerd?

Were there any other errors? Did you update to 3.3 anyway and bypassing the powerd? I wonder if there are more problems than just the powerd.