Kindle 2 fried, please help!

[Blog Kindle]

Osen,

I'm in the same boat as you are. Also tried to fiddle with fonts file and got burned.

How do you enter recovery mode on K2?

[igorsk]

Rebooting with R held down AFAIR.

[wz2b]

Originally Posted by igorsk

Rebooting with R held down AFAIR.

Let us know if that works please

[Osen]

Rebooting with home key held.

HOwever the recovery mode is not helpful. At least not until we can get igor one and plead him to figure out how to construct a recovery update properly...

[Blog Kindle]

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.

[Osen]

Originally Posted by Blog Kindle

Ok.
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.

It has to be case 3. Just try it with a blank script and you still get Error 003.

[daffy4u]

Originally Posted by Blog Kindle

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.

What the did you tell them to get them to send a replacement (you don't really have to answer that )? Maybe Osen can get a new one as well.

[Blog Kindle]

I've tried unpacking 2.0.2 update and repacking it as FB01 update - it also fails with error 003.

There should be something special that recovery updates must have...

Will keep digging a little more...

[clarknova]

Originally Posted by Blog Kindle

I've tried unpacking 2.0.2 update and repacking it as FB01 update - it also fails with error 003.

There should be something special that recovery updates must have...

Will keep digging a little more...

It seems to me that there are at least three processes involved in performing the updates:

1. powerd - the Amazon written power management daemon (not open source), besides handling part of the screen saver implementation I suspect it's what is responsible for "Recovery mode" when it is started and the home key is held.
2. The Java GUI - again no source code.
3. Shell/Init scripts - these are the only things we can be certain of what they do without going through reams of ARM machine code, or poorly disassembled Java.

A couple things:

• Can you try it with FB02 as well. The java side seems to be looking for either FB02, FC02, or FD03. Maybe that'll at least get you past the 0003 error, but probably not. For that matter, try FD03 as well.
• The shell script side shows us that the FC/FD are OTA updates and cause the system to launch into runlevel 3 to perform the update, runlevel 3 is the update script which unpacks the update and runs the scripts. However, FB is noted as being a "full update" and the system simply reboots. I would wager a guess then that the FB "full update" bins are probably supposed to contain filesystem images (See Igorsk's blog about the 6 and 7 id in the original K1 update files) however I can't say for sure -- the shell scripts only work for the FC02/FD03 bundles.