[knc1]

Originally Posted by donB006

- - - -

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.

Whooaa - - -
Please clarify.
Is (was) the DXG running the kernel and the "OS 3.1" from Yifan Lu?
OR
Is (was) the DXG running the kernel and rootfs from your K3G?

Originally Posted by donB006

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.

Once again, please be specific.
What device(s) is/was running the "custom 2.5.8 kernel"?
Are they (where they) also running the matching "custom 2.5.8 module build" (a component of the rootfs image)?

Originally Posted by donB006

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.

Please do not quote anonomous sorces of information.
Who says?
In connection with what device / firmware version series?

I have read both myself, but they have always been about different devices.
So please either quote full context or links to where you are getting that conflicting information.

Originally Posted by donB006

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.

Now your getting closer to the cause.
Since you say you fixed the problem on both devices with the same fix - the devices must have somehow been sharing the same problem.

This is beginning to sound like they where sharing the same case of:
PEBKAC

The only thing clear so far is that both devices share the same owner.

Originally Posted by donB006

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.