Hack fail to update on a k3g

[cardamon]

I think I've quite mucked things up installing and unstalling hacks on my kindle 3g. I did a dumpMessages for details. No matter which one I try now, they fail when I update, and without an error code. It's far from bricked...still works...just frustrating.

Spoiler:

120628:075108 system: I S50updater:def:wand shutdown complete
120628:075108 system: I S50updater:def:read bundle line [/mnt/us/update_ss_0.27.N_k3g_uninstall.bin]
120628:075108 system: I S50updater:def:Applying update /mnt/us/update_ss_0.27.N_k3g_uninstall.bin
120628:075108 system: I S50updater:def:Size of update: 1650 bytes
120628:075108 system: I S50updater:def:Version before update: 021-S3-061168
120628:075108 system: I _otaupexec:def:processing update /mnt/us/update_ss_0.27.N_k3g_uninstall.bin
120628:075108 system: I _otaupexec:def:version is "FC02"
120628:075108 system: I _otaupexec:def:update image checksum OK
120628:075109 system: E _otaupexec:def:signature verification failed on "/tmp/.update-tmp.5810/update-filelist.dat"
120628:075109 system: E _otaupexec:def:signature verification failed
120628:075109 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=30C:from pmic
120628:075111 system: E S50updater:def:OTA update failed (1)
120628:075111 system: I S50updater:def:Deleting OTA bundle file "/mnt/us/update_ss_0.27.N_k3g_uninstall.bin"

Spoiler:

120628:080329 system: I S50updater:def:wand shutdown complete
120628:080329 system: I S50updater:def:read bundle line [/mnt/us/update_usbnetwork_0.39.N_k3g_install.bin]
120628:080329 system: I S50updater:def:Applying update /mnt/us/update_usbnetwork_0.39.N_k3g_install.bin
120628:080329 system: I S50updater:def:Size of update: 1059934 bytes
120628:080329 system: I S50updater:def:Version before update: 021-S3-061168
120628:080330 system: I _otaupexec:def:processing update /mnt/us/update_usbnetwork_0.39.N_k3g_install.bin
120628:080330 system: I _otaupexec:def:version is "FC02"
120628:080331 system: I _otaupexec:def:update image checksum OK
120628:080333 system: E _otaupexec:def:signature verification failed on "/tmp/.update-tmp.16203/update-filelist.dat"
120628:080333 system: E _otaupexec:def:signature verification failed
120628:080333 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=31C:from pmic
120628:080335 system: E S50updater:def:OTA update failed (1)
120628:080335 system: I S50updater:def:Deleting OTA bundle file "/mnt/us/update_usbnetwork_0.39.N_k3g_install.bin

"

Then just to make sure the jailbreak was in:

Spoiler:

120628:080638 system: I S50updater:def:wand shutdown complete
120628:080638 system: I S50updater:def:read bundle line [/mnt/us/update_jailbreak_0.10.N_k3g_install.bin]
120628:080638 system: I S50updater:def:Applying update /mnt/us/update_jailbreak_0.10.N_k3g_install.bin
120628:080638 system: I S50updater:def:Size of update: 8673 bytes
120628:080638 system: I S50updater:def:Version before update: 021-S3-061168
120628:080638 system: I _otaupexec:def:processing update /mnt/us/update_jailbreak_0.10.N_k3g_install.bin
120628:080638 system: I _otaupexec:def:version is "FC02"
120628:080639 system: I _otaupexec:def:update image checksum OK
120628:080639 system: E _otaupexec:def:update*.dat not found
120628:080639 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=32C:from pmic
120628:080641 system: E S50updater:def:OTA update failed (1)
120628:080641 system: I S50updater:def:Deleting OTA bundle file "/mnt/us/update_jailbreak_0.10.N_k3g_install.bin"

Likely my own damn fault, whatever the cause. But I'd appreciate a nudge in the proper direction. And if this is covered in another thread, my apologies for not finding it first.

It's been factory reset from the menu screen, but I haven't tried anything harder than that.

[geekmaster]

How did you update? A restart will fail to finish installing hacks. You need to select "Update Your Kindle" from the settings menu, and it will only be active (not gray) if the hack update*.bin file matches your kindle. If you have firmware version 3.3, you need hacks with "3.2.1" in the file name (which you can see if you read the README file that comes with the hack).

[cardamon]

I do have 3.3, and I used the ones in this thread https://www.mobileread.com/forums/showthread.php?t=88004 and updated the only way I know how how...put the hacks in the root directory and then unmounted and went to Settings and selected Update from the menu on the Kindle. AFAIK those are the support for >=3.2.1.

0.10.N_k3g jailbreak and 0.27.N_k3g ss and 0.39.N_k3g usbnetwork hacks.

I had existing hacks, but I ran their uninstallers to upgrade to these. There's the possiblity one failed at some point, as I wasn't always watching the screen and the particular error message doesn't stick around for long.

[knc1]

Any chance you had more than one update*.bin on the machine at the same time?

[cardamon]

I made sure I only had one at a time. I won't say it's impossible, as it was late when I was noodling witth it.

[geekmaster]

Originally Posted by cardamon

I do have 3.3, and I used the ones in this thread https://www.mobileread.com/forums/showthread.php?t=88004 and updated the only way I know how how...put the hacks in the root directory and then unmounted and went to Settings and selected Update from the menu on the Kindle. AFAIK those are the support for >=3.2.1.

0.10.N_k3g jailbreak and 0.27.N_k3g ss and 0.39.N_k3g usbnetwork hacks.

I had existing hacks, but I ran their uninstallers to upgrade to these. There's the possiblity one failed at some point, as I wasn't always watching the screen and the particular error message doesn't stick around for long.

The names you gave were for the zip files. Inside them are multiple update*.bin files. The K3 has files both with and without .3.2.1 in the file name. I wanted to be sure you installed the .3.2.1 version. But the "Update your kindle" menu item should have been grayed out if you had the wrong version, and if you installed it successfully, you probably used the right one.

I do not know the error codes. NiLuJe would be the one who knows best for the "N" hacks. If he does not notice this thread, you could PM him (but give him a day to notice -- he has been active here lately). Unless somebody else who knows hack update error codes cares to provide a definitive answer.

[cardamon]

I'll do that and thanks. In the event he's unable to note the problem or a solution, would the "debricking" methods that seem to involving dding known images to the filesystem overwrite whatever it is that I might have written into it to cause this mess?

[NiLuJe]

@cardamon: Given your log, no, you didn't use the -3.2.1 jailbreak install. That's likely the root of your issues. Don't forget to restart your Kindle after the JB install, in case there's a bit of a mess of JB left after the previous uninstalls (some early versions behaved badly on uninstall, and left the system in an inconsistent state until a reboot)...

To answer the question about the error codes in details:

Yes, that's consistent with a non jailbroken device for the ss/usbnet hack (U007), and that's consistent with using the 'old' jailbreak install on firmware >= 3.2.1 (U004).

Thanks for the logs, btw, it's refreshing to actually have enough information in the first post to provide a definitive answer straightaway .

Just to make sure: Did you uninstall the jailbreak at one point? Or just the other hacks?

@GM: Unfortunately, the 'UYK' link will light up with both JB install files, so we can't use that to avoid mistakes . (It just checks the device code, so as long as there's a 'k3g' in the name of the bin file, it means it's tagged for a K3G [in this case, although it'd be pretty dumb to actually put a different tag in the filename than what the device code in the update header actually refers to ^^]).

[cardamon]

Yes. I preveriously had...Serge's 0.5.1 for >=3.2.1 devices jailbreak. Which I thought I have uninstalled.

Hmm...is it normal to see only 3,102MB free on a K3G after a factory reset? I bet I have a lot of junk hidden somewhere. Maybe /tmp/

And thanks for the thanks. I do rather feel like a brainless mook about this one, so I'm trying to approach things with a patient and deliberate manner from here on out.

[NiLuJe]

@cardamon: You might want to try rebooting before and after installing the jailbreak then, if it still fails to install .

Yep, ~3.1GB seems about right for the userstore, the rest is reserved for the system partition(s).

[geekmaster]

Originally Posted by cardamon

...
Hmm...is it normal to see only 3,102MB free on a K3G after a factory reset? I bet I have a lot of junk hidden somewhere. Maybe /tmp/

In the kindles (and many other linux boxes) /tmp/ is usually RAMdisk, so it would not affect the size of the user store (USB drive).

[cardamon]

The lack of the right build was the problem. In other words, an ID10T error. Thanks to all of you, Geekmaster and NiJuLe above all others. I knew knew to look for a k3g build so I only pulled the first one I found out of the archive. My fault.

Question: Is the appropriate uninstaller is the same regardless which you use?

[NiLuJe]

@cardamon: Yep, there's only one uninstall file for each device anyway .

[knc1]

Originally Posted by geekmaster

In the kindles (and many other linux boxes) /tmp/ is usually RAMdisk, so it would not affect the size of the user store (USB drive).

The above is probably either a typo or an intentional simplification.
But since there is a currently open problem that is related to this....

Linux does support (if optioned at build time) RAMdisk devices.

These are an area of always resident memory which may be used as any other storage media device, including having a file system put on them. Using these reduces the physical memory page pool.

In addition, there are two memory based file systems user accessible, plus many other "nodev" filesystems.

There is a ramFS which is implemented in the VFS cache buffers without any backing store, hence are always resident. The amount of VFS cache that can be used by this system is a very limited (small) percentage of the cache buffers.

The third is the tmpFS file system, also implemented in the VFS cache buffers. In the case of this file system, it has a backing store, swap. For POSIX compliance, this file system is also accessible on the device /dev/shm.
This file system is system limited in total size to the smaller of 1/2 of memory or 1/2 of (the optional) swap. The size of each instance may also be limited by mount time option.

The directory sub-trees headed by /tmp and /var/tmp are normally mounted on a tmpFS instance.
The directory sub-tree of /run in the newer FHS layout is also normally mounted on a tmpFS instance.

The above distinctions apply in the thread about running a chroot'd system.

A user may display the contents of /proc/filesystems (cat /proc/filesystems) and make note of all the "nodev" entries.

That list varies based on build-time options and what run-time modules are currently loaded but shows that the descriptions in this thread are far from exhaustive.

Note 1: /proc (and /sys) are virtual file systems, those are implemented in the data segments of the kernel's program code. (here, counting the data segments of loadable module code as the same)

Note 2: You will not see "RAMdisk" in that file system list because it is a device, not a file system.

{rant}
There is an embedded Linux development firm out there even more screwed up than lab126 who implements a swap-file in a FAT-32 file system placed on a RAMdisk device.
A really useless idea.
{/rant}

[geekmaster]

Originally Posted by knc1

The above is probably either a typo or an intentional simplification.

Intentional simplification. I realize it is mounted as a tmpfs device. But for most non-linux users, it "acts" like a RAMdisk, in that you can store temporary files in it that go away on reboot, and with no swap, it exists only in RAM. In general (not necessarily the "linux way") what I just described IS a RAMdisk (from a common layman's perspective.)

Buzzwords like "tmpFS" and deep linux technical details are just noise to most "ordinary" people, but they are powerful terminology for linux geeks. It depends on who your audience is. This is a kindle developer's forum, not so much a linux developer's forum (but "user level" linux knowledge helps, unless you want to write native mode apps that also need deeper linux developer's knowledge).