My Kindle Touch is currently stuck in the diags screens. I have gone through many posts regarding this issue and although there is some amazing information on this site, I can't seem to get them to work. Here are the things I've tried and where I've gotten stuck.

* Running Windows 7 Home
** NOTE: When my Kindle enters Diags, it always runs a MOVINAND test and tells me it passed and to send to next station. I'm not sure what this means.
*** USB device mode does work
*** I should also mention that an OTA update is what caused my kindle to enter diags mode, not something I was messing with.

2) Guide to debricking Kindle Touch V3.pdf- I get MfgTool to see the HID-compliant device, but when I put fastboot on, my computer recognizes it as an android device, and I can't locate the kindle in my device manage to try and load the Kindle-fastboot.inf driver. So no device called kindle_fastboot to be seen anywhere. But since I can get into the diags menu, I'm not sure how critical an issue this is. However, when I try to use the command line and fastboot.exe to flash mmcblk0p2_ssh.img, I get a waiting for device error.

3) I've also tried installing fastboot from the diags menu, but it still causes a waiting for device error, and I don't know how to verify that I it really is in fastboot mode. It just boots back into the same menu.

4) I've tried installing Ubuntu and doing it straight from unix but still get the issue with waiting for device.

5)I've tried using the Runme.sh file as well, but once I reboot, the file is gone and there is no Runme.done or log.txt file to be seen anywhere.

I think that's all I've tried so far. I appreciate any help and I apologize if I missed anything obvious or if my issue has already been resolved in another post. I searched before I posted, I promise.

In Windows in device manager the Kindle will not be shown as "Kindle", but like something else, probably something like "Android device", if you have installed Android drivers.
In Linux, you need to run fastboot under root by:

sudo ./fastboot flash diags mmcblk0p2_ssh.img

If you have problems with root password, type "sudo passwd" in terminal and type new password which you need to remember and which you will type when executing fastboot after that.

Thanks for your advice. However once I put a blank device_info.xml in the diagnostic_logs folder, I get another error stating:

Mac address and manufacturing code do not match

Mac address:

**************

Manufactuing code:

Invalid <====== Yikes!

I tried doing some research but couldn't find any help with this problem. Thanks in advance everyone!

You can rewrite those values with correct values with the diags idme command. Do not change your serial, pcbsn, or mac address. Copying the Mfg code from another K5 may be okay. Use the diags "idme -d" command to write them.

You can rewrite those values with correct values with the diags idme command. Do not change your serial, pcbsn, or mac address. Copying the Mfg code from another K5 may be okay. Use the diags "idme -d" command to write them.

Thanks GeekMaster, seems like I'm back to square one: trying to get SSH to work.

Thanks GeekMaster, seems like I'm back to square one: trying to get SSH to work.

There is also a diags command to rewrite them from an XML file, but I do not know what the format is.

On my first K4, all the idme vars got replaced with spaces, and it need to know the PCBSN to know how to init RAM. I had to create a custom u-boot that WROTE my known values into mmc. Then I copied the partitions and kernels from my new K4 onto the old one. They both work now... The dead K4 was my main reason for figuring out how to create a custom MfgTool profile (later published in the "select boot" thread).

Can you boot to main with MfgTool? Can you flash diags_ssh with fastboot so you have SSH in diags?

There is also a diags command to rewrite them from an XML file, but I do not know what the format is.

On my first K4, all the idme vars got replaced with spaces, and it need to know the PCBSN to know how to init RAM. I had to create a custom u-boot that WROTE my known values into mmc. Then I copied the partitions and kernels from my new K4 onto the old one. They both work now... The dead K4 was my main reason for figuring out how to create a custom MfgTool profile (later published in the "select boot" thread).

Can you boot to main with MfgTool? Can you flash diags_ssh with fastboot so you have SSH in diags?

There is now a 5.1.0 main image with jailbreak and ssh pre-installed.

Using mfgtool, I tried flashing diags, fastboot, and main. Each will say they are successful, but only the diags flash results in a reboot of my kindle.

When I try to use fastboot, I'm stuck "waiting for device".

It seems my kindle really likes to be in diags mode and doesn't want to let me ssh into it and fix it.

Using mfgtool, I tried flashing diags, fastboot, and main. Each will say they are successful, but only the diags flash results in a reboot of my kindle.

When I try to use fastboot, I'm stuck "waiting for device".

It seems my kindle really likes to be in diags mode and doesn't want to let me ssh into it and fix it.

Unless you have hardware problems or a damaged bootloader, or download or storage problems causing corrupt image files, there is no (known) reason for this debricking method to fail.

The fastboot problem could be that libusb-win32 is not configured properly, or that fastboot mode is dropping out because of a USB reset. Try saving fastboot mode in diags (install fastboot bundle). Then reboot should go directly to fastboot mode. Try using a linux fastboot program.

EXACTLY what commands did you use and what were the results? We have had plenty of problems lately from people saying they followed the instructions, only to find out later that they flashed the wrong files to the wrong partitions. Seeing what you did can help diagnose this problem. Just SAYING that you followed the instructions and they did not work places you in the same situation we saw for people who said the same thing, but skipped steps or flashed the wrong images.

Unless you have hardware problems or a damaged bootloader, or download or storage problems causing corrupt image files, there is no (known) reason for this debricking method to fail.

The fastboot problem could be that libusb-win32 is not configured properly, or that fastboot mode is dropping out because of a USB reset. Try saving fastboot mode in diags (install fastboot bundle). Then reboot should go directly to fastboot mode. Try using a linux fastboot program.

EXACTLY what commands did you use and what were the results? We have had plenty of problems lately from people saying they followed the instructions, only to find out later that they flashed the wrong files to the wrong partitions. Seeing what you did can help diagnose this problem. Just SAYING that you followed the instructions and they did not work places you in the same situation we saw for people who said the same thing, but skipped steps or flashed the wrong images.

I apologize for not providing enough information. I will focus each post on a technique I tried and will provide as much detail as possible.

Method: Fastboot Install from Diags

- Selected Fastboot Bundle Install
- Kindle asked: Are you sure? So I selected D) To continue
- After 8 secs, Kindle reboots and I get the Amazon Tree screen
- I then get a "Enter MOVINAND Test" screen
- Then it says DIAGS PASSED Send This Unit to the Next Station
- Selected Exit which brings me back to the Exit, Reboot, or Disable Diags screen

Edit: This was all done with the kindle plugged into my laptop for charging purposes.