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

[knc1]

Originally Posted by newman

I mean this:

dd if=/dev/zero of=/mnt/base-us/swapfile bs=1M count=64
chmod +x /mnt/base-us/busybox
/mnt/us/busybox mkswap /mnt/base-us/swapfile
/mnt/us/busybox swapon /mnt/base-us/swapfile

It's the only combination of /mnt/us × /mnt/base-us which worked for me. It does not work for me with /mnt/us/ (not sure which step exactly).

Is that with or without the USB cable connected to a PC?
If yes, what PC? What PC O.S.?

======

Also try this one please =

Find next available loop device:

losetup -f

Using the device just found above rather than the /dev/loop0 shown in the following, do:

dd if=/dev/zero of=/mnt/base-us/swapfile bs=1M count=64
losetup /dev/loop0 swapfile
mkswap /dev/loop0
swapon /dev/loop0

If any of those four commands are not shipped with the firmware, then precede them with the /mnt/base-us/busybox magic, same as you have been doing.

[SnowLeopardW]

Succeeded!
Enable to recognize the .azw3 file, but still can not open it.
Already without the DRM.

[Image violates Posting Guidelines for size - MODERATOR]

[Dr. Drib]

Moderator Notice

SnowLeopardW
Please take a few moments to read our Posting Guidelines, in particular the part about the maximum image size allowed (600x600 pixels). Images that violate those guidelines will be deleted.

It is every member's responsibility to read our Posting Guidelines and follow them.

Thanks.

[SnowLeopardW]

[newman]

SnowLeopardW: Congratulations! I thrilled! Were you using my guide?

WRT AZW3/KF8: Use this guide: https://www.mobileread.com/forums/sho...46#post3160846. The safest way how to try it is to `mount --bind ...` the edited fb.modes to /etc/fb.modes and start webreader manually and if it works make it permanent as is described in the guide. Let me know how it went.

[newman]

knc1: Thanks. Will try it later. It's: Fedora 22 on Toshiba Satellite 855 with USB2 cable attached.

[knc1]

Originally Posted by newman

knc1: Thanks. Will try it later. It's: Fedora 22 on Toshiba Satellite 855 with USB2 cable attached.

In USB networking mode over the USB cable -
And you switch into and out of USB networking mode **without** the USB cable attached.

That should not interfere with the FUSE layers.
I.E: You should be able to access both /mnt/base-us and /mnt/us

Its only if your in USB storage mode that there is interference.

= = = =

There is one other far-out possibility -
Mis-matched kernel and kernel modules.

A (very) few of the kernel modules are included in the initramfs image with the kernel.
Those would load into kernel space from initramfs.

The majority of the kernel modules are only in the rootfs image.

So it could be possible that the device isn't booting the 3.4.2 kernel (or a compatible build).
But your kernel message file (dmesg) should be filled with errors whenever it tries to load the mis-matched module(s).

[SnowLeopardW]

Originally Posted by newman

SnowLeopardW: Congratulations! I thrilled! Were you using my guide?

WRT AZW3/KF8: Use this guide: https://www.mobileread.com/forums/sho...46#post3160846. The safest way how to try it is to `mount --bind ...` the edited fb.modes to /etc/fb.modes and start webreader manually and if it works make it permanent as is described in the guide. Let me know how it went.

Yeah. I followed the guide of yours step by step and finally succeeded. It’s really helpful! And now, the webreader can be automatically launched every time when I restarted my Kindle. The .azw3 file shows perfectly on my DXG both in landscape and portrait mode now. Thank you so much!

[newman]

SnowLeopardW: Glad you like it! One more thing, it's possible to enable Active Content on DX with 3.x FW. Unless you live in the US (and therefore you are able to buy AC from Amazon) the only useful app is KUAL. But I can't find the link to the guide..

[knc1]

Ah...
s/enable/re-enable/

Because active content (and KUAL) works on the series 2.x devices (K2, DX, DXG).
It was designed to work on everything except the K1.

[newman]

SnowLeopardW: This is where you'd start: https://www.mobileread.com/forums/sho...31#post1747631, if interested in KUAL. But read the follow-up comments in that thread since the thirst ZIP is broken and it seems to me that those "magic numbers" differ Kindle to Kindle (DX being different from K2, or something).

[donB006]

I decided to try this on my DXG still at 3.1 for the last few years. My need is mostly for the TLS fixes.

I failed to update from 3.1 to 3.3 because of a U007 error. This might be due to my jailbreak except I just installed USBNet and made a dxg 3.1 rootfs.img backup before trying the update. My jailbreak might still be from when I first followed Yifan Lu's instructions to take my KDX from 2.5.8 to 3.1 OS and could be the problem.

I believe I edited the 3.3 update-06-558700031-611680021.bin correctly for the dxg:

Signature: FC02 (OTA update)
min version: 558700031
max version: 611680021
device code: 09
optional: no
md5 of tgz: 4b722e59ad163c1e507f2f51716124ec

The update failed with U007 error. I had this same error when trying to update my K3 from 3.1 to 3.4.2 and finally had to revert to 3.0.2 using the pastebin rootfs with k3flasher and then was able to install the Amazon updates without error. These U007 errors stop my efforts. All I can think of is trying to find the 3.2.1 update and starting from there.

The attached ;dumpMessages doesn't give much help. Also, I was wondering if you could post your ;dumpMessages from the DX with 3.4.2 to show how the DX likes the update? I am prepared to return to 3.1 if 3.4.2 has problems except now I can't get to 3.4.2.

[knc1]

Originally Posted by donB006

- - - -
I had this same error when trying to update my K3 from 3.1 to 3.4.2 and finally had to revert to 3.0.2 using the pastebin rootfs with k3flasher and then was able to install the Amazon updates without error.
- - - - -

See those lines with the word "ERROR:" in them?

Those indicate that you do not have a matching kernel/rootfs pair.

You **MUST** install the kernel and the rootfs as a **matched pair**!

[donB006]

Originally Posted by knc1

You **MUST** install the kernel and the rootfs as a **matched pair**!

Thank you for the reply. I want my DXG to run perfectly and don't like those ERRORs either. I checked for the missing modules and found they were not being used at least during usbNetworking:

Module                  Size  Used by
g_ether                28364  0 
ppp_async              12484  0 
crc_ccitt               1952  1 ppp_async
ppp_generic            25492  1 ppp_async
slhc                    6624  1 ppp_generic
mxc_alsa_pmic          36480  1 
snd_pcm                84421  1 mxc_alsa_pmic
snd_page_alloc          8520  1 snd_pcm
snd_timer              24740  1 snd_pcm
snd                    49188  5 mxc_alsa_pmic,snd_pcm,snd_timer
mma7660F               28376  0 
mxc_keyb               18968  1 
uinput                 10816  0 
fuse                   48404  2 
arcotg_udc             48724  1 g_ether
charger                28992  1 arcotg_udc
mwan                    8052  1 ppp_async
eink_fb_shim          126620  0 
eink_fb_hal_broads    370172  0 
eink_fb_hal            58884  6 eink_fb_shim,eink_fb_hal_broads
fiveway                20352  1

The expected modules must not be there even without usbnetworking when the update routine is shutting down the services and so causes the ERRORs.

The kernel from Yifan Lu and the OS 3.1 from Yifan Lu should be a matched set because I haven't flashed any different kernels or rootfs partitions since I first used my K3G to upgrade the DXG to 3.1 so I think that much is normal. I would be surprised if everybody didn't have those errors with the DXG. Of course, the 3.1 OS has some 2.5.8 features with the custom 2.5.8 kernel.
I now suspect the ERROR might be because there is no WIFI or the 3G WAN was turned off and the Lab126 didn't test for that before trying to remove the modules. Maybe they have something to do with the recovery kernel. Whatever is running the rmmod in preparation for the update still allows continuing into the update so I think there could be another reason. I tried to get more information with ;debugOn and then Update with the same result. I think this is the relavent part:

151102:162349 system: I S50updater:def:wand shutdown complete
151102:162350 system: I S50updater:def:read bundle line [/mnt/us/update-06-558700031-611680021.bin]
151102:162350 system: I S50updater:def:Applying update /mnt/us/update-06-558700031-611680021.bin
151102:162350 system: I S50updater:def:Size of update: 1926999 bytes
151102:162351 system: I S50updater:def:Version before update: 031-S1-055870
151102:162351 system: I _otaupexec:def:processing update /mnt/us/update-06-558700031-611680021.bin
151102:162351 system: I _otaupexec:def:version is "FC02"
151102:162353 system: I _otaupexec:def:update image checksum OK
151102:162357 system: I S50updater:def:Deleting OTA bundle file "/mnt/us/update-06-558700031-611680021.bin"
151102:162357 init: Switching to runlevel: 5

That doesn't help at all. The update lasts for 7 seconds until the upgrade is unsuccessful and issues the U007 reason. I still suspect the jailbreaks and am now going to investigate. I remember reading about a leftover certificate that can cause the U007. Some say once the Kindle is jailbroken there is no reason to uninstall or reinstall the jailbreak and some say the jailbreak should be kept up-to-date. At least I have a backup now in case I spoil my current installation.

There is a possibility the U007 is caused by my history with the KDX and maybe with the K3G before the DXG upgrade. I have used various hacks like usbNetworking, launchpad, readabilitymod, updatesprovider, screensaver and readers like Duokan, Librerator, kpdfviewer and coolreader3. Those are now gone except for usbNetworking and launchpad. I have tweaked the DXG on my own only in the area of the logs where I turned off the logging until just decided to try the 3.4.2 upgrade. When changing the logging I might have modified a couple of files that Amazon checks for changes. I don't know. This is a confusing mystery.

Maybe I should read all of the Kindle Developers Corner again because I know others have had the U007 problem. I need to look into the jailbreaks. Thanks for the attempt knc1.

[newman]

I am not sure what's your current problem. Are you unable to upgrade from 3.1 upwards, or are there problems with kernel modules on boot? If the former, I'd suggest to add following to the respective upgrade script which is in the OTA update bin, and see what happens:

set -x
exec > /mnt/us/my-upgrade.out
exec 2> /mnt/us/my-upgrade.err

(For more see the guide in comment #0.)