[geekmaster]

Just a warning. I completely bricked a k4nt so it will probably need a JTAG cable to fix it. All I did is boot to diags, export and delete /mnt/us/ENABLE_DIAGS, then in the diag menu I selected the "disable diagnostics" menu item.

The display has shown the highlighted item "Q) To continue - FW LEFT" on the "Disable Diagnostics" page since then. It died when I pressed the 5-way LEFT button. It is now stuck in USB/HID mode. Connecting to the serial port and pressing the power button shows u-boot "bailed!" because the serial number and board ID are now both "1", and u-boot cannot initialize hardware for an unknown board type. Just a quick press of the power button makes u-boot restart, always giving the same "bailed!" error message.

There appear to be dangerous bugs in diagnostics, so beware!

Luckily, using diagnostics mode is no longer required to jailbreak a K4NT. Use ixtab's data.tar.gz method instead.

My new k4nt just arrived yesterday. The old one will just be for spare parts, until I have time to learn more about JTAG (which is supported by my "bus pirates").

P.S. The Freescale "usb downloader" tool claims that it successfully installs and executes code in my bricked k4nt RAM using USB/HID mode, so if I just had the correct payload, perhaps I can write good values into the board ID and serial numbers, so it can boot up enough to debrick it using other means.

UPDATE: Be VERY careful with the serial port cable attachment on the k4nt. I accidentally ripped the tiny TxD and RxD pads completely off the circuit board with very light upward pressure on my serial cable. I should have mechanically secured the cable to the circuit board with adhesive tape. There are some surface mount resistors mounted next to the missing pads, so I can probably solder my TxD and RxD cables there next time I need it. I will verify these secondary connection points using my new k4nt, when I get around to removing its back cover.