[perconte]

Originally Posted by ixtab

I'm afraid that I will only repeat the instructions which are already there in Kubrick.... but anyway - on the Kindle Touch:

1. Press the Power button for a loooong time, like 30 seconds. (If it's connected to a computer: until the LED turns off)
2. While KEEPING the power button pressed, also press the HOME button
3. Release the power button, while KEEPING the HOME button pressed.
4. Release the HOME button after a second or two.

Unless something is terribly wrong with your Kindle (hardware fault?) this WILL put the Kindle into USB downloader mode. In fact, at this point, the Kindle SoC state is as close to the hardware as we can ever get, and that particular combination (starting up with the home button pressed) MUST put the chip into USB downloader mode.

Thank you for the instructions, but I tried several times and nothing happened. I mean, in the 3rd step when I release the power button, while the home is pressed, the LED turns on (orange colour). And after that, I have to release only the home button but Kubrick still doesn't recognize it.

Originally Posted by knc1

And the USBdownloader mode does not modify the screen on the Kindle.

Thanks for de info

Originally Posted by ixtab

... the only other problem I could think of is a USB problem on the host side, i.e., the Kindle actually entering USB downloader mode, but Kubrick not recognizing it. (Similar to the optical drive driver issues mentioned in earlier posts).

If you keep having problems, please press Alt+F2, login as root (no password), run the following command:

lsusb

and post its output here.

OK, I will try it now. Thank you
Edit: Here you have the output

root@kubrick: ̃ # lsusb
BUS 001 Device 002: ID 8087:0020
BUS 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
BUS 001 Device 003: ID 0408:2fb1 Quanta Computer, Inc
BUS 002 Device 002: ID 8087:0020
BUS 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
BUS 002 Device 003: ID 0951:1660 Kingston Technology

Originally Posted by knc1

bad cable, bad port
Both have been encountered in the past.

Try a different port on your pc.
Try a different USB cable if you have one.

I will try it also if the previous one fails, thank you.