azuwis was right, I've added a LF to packages.lst and was able to create a BIN file for the DX Graphite. I just ran the first script under Ubuntu.

However, I understand there is a change NiLuJe's jailbreak doesn't work, and we need to use Yifanlu's? My DXG has been jailbroken with NiLuJe's jail break 0.6. Yifanlu's, would that be 0.4, last updated 11/02/28?

@tekkasit: Argh. Yep, you're right, fixing that right now, and it probably affects a bunch of other hacks, too. >_<"

EDIT: v0.7.N should now *really* play nice with this ;).

Yea, see the known bugs on the first post and the readme. For some reason, TTS saving crashes every time. The first post and readme shows how you can bypass it.

First I want to thank Yifanlu for an impressing work both with the jailbreak and this promising enterprise. I have a Kindle DXG with firmware 2.5.8 and serial B009 and a Kindle 3, 3G+Wifi with firmware 3.1 and serial B00A. I am so annoyed that the DXG hasn´t got firmware 3.1 because it is much better.

I would like to try your hack but have two problems.

1. As azuwis pointed out "packages.lst in kindle-updater-beta2-src.zip has no EOF or new line, this lead to the missing update_dxg-2.5.8-prepare_kindle.bin". Could someone recompile since I don´t know how to compile the source code on a Windows 7 machine.

2. I am afraid of bricking my Kindle DXG. How is it possible to restore old firmware if the new one doesn´t work. The instructions for restoring in the ReadMe file is given only for Linux. How would you do it in Windows 7.

Yifanlu, please continue with your excellent work. It would be fantastic to get a DXG with firmware 3.1. I don´t understand why Amazon doesn´t release it.

The reason I didn't compile it yet is because one tester found a bug that prevents the kindle from working. Good news is, he also tested the backup recovery process and it works, so it would be really hard to brick your kindle once you flash my custom kernel correctly. Even if you brick your kindle, you can now recover with the recovery package.

This is true. I get the "Your Kindle Needs Repair" error right after successfully updating to 3.1, so it makes it so it won't boot (on a k2i).

The recovery kernel is freaking amazing though - yifanlu has his act together.

Hi guys I am so glad to have found this post.

Currently I have a kindle DXG serial B009 and I have a linux machine.

I am willing to beta test but I dont have access to the 3.1 roofts image file.

Could someone be kind enough to PM it to me. I am hoping to get 3.1 running.

However in the updater file I downloaded from the 1st post of this thread I dont see a file for the DXG are there still bugs being worked out?

yifanlu, I tried with 'NO_TTS' file (with no extension) put on the root, and overwrite with the original 'rootfs.img'. But it still failed at 'saving tts files'.

Sat Jul 31 08:10:31 SGT 2010: checking for enough free space to continue
Sat Jul 31 08:10:31 SGT 2010: mounting rootfs image to /tmp/.rootfs.5392
Sat Jul 31 08:10:31 SGT 2010: retrieving filelist and patches
Sat Jul 31 08:10:31 SGT 2010: saving required files to /tmp/.save-root.5392.tar
Sat Jul 31 08:10:31 SGT 2010: removing old files from rootfs image
Sat Jul 31 08:10:36 SGT 2010: copying new files to rootfs image
Sat Jul 31 08:17:39 SGT 2010: saving tts files

Do you have any suggestion?

I've updated the packages to include DXG and changed the "keep file" list to include WAN firmware stuff.

Thanks Yifanlu for the updated package. Step 1 to create rootfs image went well. Unfortunately I had similar problem as Tekkasit with step 2. Failed on saving TTS. Tried to reset and also put a "NO_TTS" file in root. Then it still ended prematurely with nothing in output folder except following make-package.log file:

Sat Jul 31 02:04:41 GMT+02:01 2010: checking for enough free space to continue
Sat Jul 31 02:04:41 GMT+02:01 2010: mounting rootfs image to /tmp/.rootfs.5400
Sat Jul 31 02:04:42 GMT+02:01 2010: retrieving filelist and patches
Sat Jul 31 02:04:42 GMT+02:01 2010: saving required files to /tmp/.save-root.5400.tar
Sat Jul 31 02:04:48 GMT+02:01 2010: removing old files from rootfs image
Sat Jul 31 02:04:52 GMT+02:01 2010: copying new files to rootfs image

I tried it two times with same results. Any ideas?

I have a K3 3g+wifi outside US & Canada. I tried several times of create update. All failed:

I even put a NO_VALIDITY_CHECKS on the root. It wont work.



Sun Apr 24 01:46:59 EST 2011: checking for enough free space to continue
Sun Apr 24 01:46:59 EST 2011: mounting rootfs image to /tmp/.rootfs.6446
Sun Apr 24 01:47:02 EST 2011: retrieving filelist and patches
Sun Apr 24 01:47:02 EST 2011: device support files not found, exiting
Sun Apr 24 01:53:33 EST 2011: checking for enough free space to continue
Sun Apr 24 01:53:33 EST 2011: mounting rootfs image to /tmp/.rootfs.11146
Sun Apr 24 01:53:33 EST 2011: retrieving filelist and patches
Sun Apr 24 01:53:33 EST 2011: device support files not found, exiting
Sun Apr 24 02:16:17 EST 2011: checking for enough free space to continue
Sun Apr 24 02:16:17 EST 2011: mounting rootfs image to /tmp/.rootfs.8344
Sun Apr 24 02:16:17 EST 2011: retrieving filelist and patches
Sun Apr 24 02:16:17 EST 2011: device support files not found, exiting

It seems like you didn't use the new version of the prepare kindle package to generate the rootfs.img

Yifanlu, I think I have found the main problem. The citation marks are missing when FILES are set to empty string in "copy_new_files()" procedure in file "make-package.ffs":

FILES=""
for file in ${SKIP_TTS_FILES}; do
/bin/umount /usr/share/nuance/data/$file
FILES="${FILES} data/$file"

I also found out that it seems to be important to not only replace the rootfs.img and do a reboot if Step 2 (Create updater) fails, but in addition do a software Restart by pressing Menu/Settings/Menu/Restart to try a fresh install. However, I am not sure if this is necessary now after inclusion of the missing citation marks.

I use Cygwin in Windows 7 with OpenSLL and Python packages to run the script to compile the binaries using "bash create_packages.sh". However, despite that the binaries in the beta2-2 version were compiled without error I couldn´t use them to update the Kindle (The Update option in the Settings menu was greyed out). I had to combine the make-package.ffs file from beta2-2 version with the create_packages.sh in alpha version to get binaries with Cygwin that were acceptable for the Kindle.

I am now creating the update package for the DXG on the non-US Kindle Wifi+3G. It has passed the critical "Saving tts files" stage and is currently compressing the image. I takes a loooong time but I am optimistic that it now finally will generate an update binary. Then I will try to update the DXG with it.

The creation of the update package was successful. However after installation of the package on the DXG the DXG booted only halfway after which "Your Kindle need repair"-error occured. At the right bottom it said "battery". Maybe it is procedures which are related to the battery which are incompatible since the DXG and Kindle 3 have different batteries.

Anyway, fortunately the recovery console worked and the DXG was put back to life with old 2.5.8 firmware. A software restart was necessary to also get the web browser to work again.

Would it be possible to upgrade firmware 2.5.8 with a smaller subset of v 3.1 e.g. only the webbrowser?

Thanks for the tips! I have another tester who is getting the same error as you and I suspect that the cause is the firmware not reading the hardware battery voltage. Unfortunately, there is little I could do apart from blindly guessing at this point. I do not have a K2i or DX to test with, so it is hard to find out exactly what is wrong. Maybe if you (or anyone else) rip a copy of the /sys structure so I can see what the hardware structure is on the new Kindles, it could help a bit. I think doing something like "find /sys > /mnt/us/sys.txt" via SSH/usbNetwork/recovery port I've been scanning eBay for a while now trying to find a cheap broken K2i or DX to test with, but unfortunately, they're all > $40, which is too much. Right now, I know that it works 99% (just a bit of installer gliches) on the K2 US, but that's the only hardware I can test with.