Kindle Touch Bricked!

[somkk]

Hi All!!

I have a new Kindle Touch 4th Gen(Firmware - 5.0.4)!
Jailbreak not installed.

In hope of changing the screensaver, I enabled diagnostics.

Enabled USBnet on the Kindle, and set an appropriate IP address in Windows.

Then the kindle was detected on win XP as a RNDIS(?) network device.
I installed the drivers etc, and got a new network connection.

However, I still get the error (Fata Error: Connection refused) in Putty for both SSH & Telnet connections.
All firewalls are disabled, and no anti-virus is installed.

Tried with Kindle-wifi disabled, and used the same subnet mask on PC & Kindle.
Still can't connect.

Am able to ping the kindle's ip though1

Tried to disable diagnostics, and got an error "device_info.xml not found: Plz check your settings"

PLz advise, how do I get out of this mess ?

Preferably:
1) Preferably enable SSH, change the screensaver, and restore to normal.
OR
2) Disable diagnostics and revert to normal, without changing screensaver.

Tx a lot!

[somkk]

Restored to normal mode using MFGtool.exe!
Thank you geekmaster!!

But after reboot, Kindle again goes to diagnostic mode.
How do I go back to "normal" mode ?

Tx!

[somkk]

Deleted the "ENABLE_DIAGS" file as well
Still keeps restarting into Diagnostics mode everytime!

I have SSH access now!
How do I go back to "normal" mode ?


Sorry about the number of posts, just that is a new Kindle, and I'm not ver happy about it!

Tx!!

[geekmaster]

Originally Posted by somkk

Hi All!!

I have a new Kindle Touch 4th Gen(Firmware - 5.0.4)!
Jailbreak not installed.

In hope of changing the screensaver, I enabled diagnostics.

Enabled USBnet on the Kindle, and set an appropriate IP address in Windows.

Then the kindle was detected on win XP as a RNDIS(?) network device.
I installed the drivers etc, and got a new network connection.

However, I still get the error (Fata Error: Connection refused) in Putty for both SSH & Telnet connections.
All firewalls are disabled, and no anti-virus is installed.

Tried with Kindle-wifi disabled, and used the same subnet mask on PC & Kindle.
Still can't connect.

Am able to ping the kindle's ip though1

Tried to disable diagnostics, and got an error "device_info.xml not found: Plz check your settings"

PLz advise, how do I get out of this mess ?

Preferably:
1) Preferably enable SSH, change the screensaver, and restore to normal.
OR
2) Disable diagnostics and revert to normal, without changing screensaver.

Tx a lot!

The diags "Enable USBnet" does not enable USBnet until you press X) to exit from that menu. Then it takes about 20 seconds for the USB network to initialize before you can use it. Did you exit? Menu selections in diags are N) U) Z) X).

It works AFTER installing the mmcblk0p2_SSH.img from the SelectBoot first post.

The factory diags partition is missing the dropbear files needed for SSH, but even without those missing files the kindle is pingable (but no SSH).

[geekmaster]

Originally Posted by somkk

Restored to normal mode using MFGtool.exe!
Thank you geekmaster!!

But after reboot, Kindle again goes to diagnostic mode.
How do I go back to "normal" mode ?

Tx!

In diags main menu, use "Disable Diagnostics" from the "Exit" menu. Be sure to select "Continue" after disabling diags. It should then reboot to main.

[geekmaster]

Originally Posted by somkk

Deleted the "ENABLE_DIAGS" file as well
Still keeps restarting into Diagnostics mode everytime!

I have SSH access now!
How do I go back to "normal" mode ?


Sorry about the number of posts, just that is a new Kindle, and I'm not ver happy about it!

Tx!!

The diags mode is set TWO ways (ENABLE_DIAGS file, and idme bootmode var == "diags"). The "disable diags" menu item only works if you still have an ENABLE_DIAGS file.

Now that you have SSH, at a linux command prompt in the kindle, you can type:

rm /mnt/us/ENABLE_DIAGS
idme -d --bootmode main
reboot

... or you can do these things from the "Disable Diagnostics" exit menu, as mentioned above (but this menu item only works if your idme bootmode var == "diags" *and* you have an ENABLE_DIAGS file).

The above commands typed in an SSH shell *always* work.