MobileRead Forums - View Single Post

littelbro14 · 11-08-2012, 10:35 PM

So I've searched this entire thread for a solution to this issue. I'm not sure if I'm missing something, but I still haven't found one. I'm on Ubuntu 12.10, 64-bit. I compiled k3flasher from source (couldn't get the provided binary to work, not sure why), and I extracted the RAM kernel myself, directly from the latest ATK exe. Here's my in/output.

Code:

root@TARDIS:/home/colten/Downloads/k3flasher# ./k3flasher mx35to2_mmc.bin program 0x00041000 kernel.bin
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.

Any help on this would be fantastic....

11-08-2012, 10:35 PM	#178
littelbro14 Junior Member Posts: 2 Karma: 10 Join Date: Nov 2012 Device: Kindle 3 (Keyboard)	So I've searched this entire thread for a solution to this issue. I'm not sure if I'm missing something, but I still haven't found one. I'm on Ubuntu 12.10, 64-bit. I compiled k3flasher from source (couldn't get the provided binary to work, not sure why), and I extracted the RAM kernel myself, directly from the latest ATK exe. Here's my in/output. Code: root@TARDIS:/home/colten/Downloads/k3flasher# ./k3flasher mx35to2_mmc.bin program 0x00041000 kernel.bin I: found suitable device E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes. I: above error can be ignored, it's due to the device being in ROM kernel mode I: RAM kernel should be running now. Trying to re-open device: . I: got it. E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes. E: aborting. It is suggested you power-cycle the device. Any help on this would be fantastic....