Ok.
I'm at the same point. In recovery mode it doesn't recognize the FC02 updates, when I rolled FB01 update it tries to install it and immediately fails with error 003. I tried putting ls > /mnt/us/ls1.txt at the very start of the script and nothing happens - when I reboot the Kindle drive doesn't have ls1.txt and update bin is gone as well.
This leads to 3 possibilities:
1) /mnt/us is not mounted when the update runs, is mounted elsewhere or is not writable when the update runs (although the update itself does get deleted somehow) - LIKELY
2) ls is not available when the update runs - NOT LIKELY
3) updater refuses to run the shell script with the code. either it expects some additional metadata, checksums, etc or specific name for the script.
I assume that if we could take a look at the recovery mode image which is not part of the sources as far as I can tell we could figure out what is missing and what error 003 means.
Another thing that surfaced - is that in normal boot mode the Kindle drive is not accessible anymore - I can see the drive letter but there is no filesystem. Sometimes it would appear after several minutes - sometimes not. It's almost as if process running it is deprived of CPU.
Everything works fine in recovery mode.
I called Amazon and replacement unit is already on it's way. It's actually cool that their warranty has cross-shipping and overnight shipping.
So if I don't get anywhere by tomorrow morning I'll pack it up and ship it away. As much as I like to mess with technology I miss my books and need them for my work.
|