|
But I think it is also what's being used in Kubrick. So it will probably expose the same behaviour. I don't think that breaking the device via ATK is easily possible. Then, I'm skeptical why the poster was able to use "0x..." in the ATK input field - the "x" isn't a valid hex char and I think ATK wouldn't work in such a case. So I guess the error report misses some parts. Maybe they involved frying the USB port on either the Kindle or the Host, maybe it's just a bad USB cable. Don't know. Or it might simply not been put into USB downloader mode properly again. I'd suggest to hang on to Kubrick (to rule out other error possibilities) and try with other USB ports and cables.
|