[geekmaster]

It is a K5 with 3G. I tried ALL the K5 variants that kindletool creates. And a K1 (because I had it), and then a renamed XML file. All deleted immediately on USB ejection on this K5 5.1.2 (airplane mode, then kubrick, KUAL, backdoor locked, 3G on to test lock -- no background OTA update, so backdoor lock worked).

Question: do I need a different update type? Now using:
..\..\kindletool create ota -d k5g * ../Update_autorun_k5g_0.1.GM_install.bin
from the folder containing only my install.sh script.

EDIT: Ahh... I see... You used OTA2 for K5 packages. I will try that now.

EDIT: Hmm... With OTA2 it fails with: "Error opening temp file: Invalid argument. Cannot write update to output." Probably another instance of trying to write to drive root instead of local directory. Need more of that patch of mine we added? Create OTA works, but create OTA2 fails.

EDIT3: I copied your K5 Dummy install, and it survived USB eject and replug. The K5 must validate any update packages it finds on userstore immediately after ejecting USB from a host PC. I will eject again and try UYK. Yes, it ran. So until we have a good win32 kindletool that uses non-root temp files for OTA2 updates, it looks like I need to use a linux version. My old K1 firmware works fine with OTA updates, but that may change after I update to newer firmware.

EDIT4: Nope, don't see it in the latest kindletool source. HOWEVER, I did see this file: kindletool_create_tarball_a03440 left sitting in my install directory along with install.sh, and I did see source code trying to MOVE tarball files to temp, so perhaps my win32 patch is causing this to fail while moving a tarball onto ITSELF in the current directory? Okay, perhaps that "." we added for win32 needs to change to ".." (which requires the current dir be at least two levels deep from root.